AnsweredAssumed Answered

Replacing ACT_ID_USER table

Question asked by wesley on Aug 9, 2011
Latest reply on Aug 11, 2011 by jbarrez
I'd like to get a push to the right direction. What i'm trying to achieve is to customize activiti to use my own users table instead of the default ACT_ID_USER table. My question is around how far in customizing everything should I go?

I've been thinking to

1. replace mappings.xml (and initializing this from custom configuration class extending StandaloneProcessEngineConfiguration) to include my own SQL for User.xml entity, and pretty much keeping everything else as they are

2. replace mappings.xml to include my own entity called the Identity.xml for a new IdentityEntity class (implementing User and PersistentObject) and then extend UserManager with my own code that works with the IdentityEntity instances

3. replace mappings.xml to include my own entity together with my own IdentityEntity class but instead of extending UserManager I would create a new IdentityManager that extends AbstractManager (to get my own api more aligned with my DB table). This option means that I also need to extend IdentityServiceImpl and many of the commands to reflect the new IdentityManager class.

4. do one of the above, but not mess with mappings.xml and custom configuration class that initializes the sqlSessionFactory – dunno what would be a good alternative though

So which way should I go? Would option #3 even work? Any other suggestions?

I have searched the forums and modifying mappings.xml is not mentioned, only changing the UserManager. However, I see this as the only way to go if I want to reuse the DB session and use my own tables to do the queries.

Outcomes