EntityManagers and business logic code

[dzmitry]

Guys, what do you think that would separate the business logic contained in the EntityManager's classes and work directly MyBatis (SQL) code?

I think the current code has 2 problems:
1) EntityManager's do not have interfaces.
2) Interaction with MyBatis not made ​​on a separate level.

I plan to to develop pilot implementation Activiti for NoSQL.
But the problems described above make complicate synchronization branches in the future.

What do you think about it?
I will be glad to hear your opinion.

Thanks,

[frederikherema1]

This is core engine stuff and it's done this way to keep the abstraction and overhead to a minimum. There are currently no plans on refactoring this layer as we don't see the immediate need and we have limited bandwidth in the team.

[sumeraxe1]

This will probably not answer your question directly, but there's usually no need to do that. The only benefit of having authorised user in Activiti is that you have variables like "initiator" populated automatically - apart from that there is no direct link between Activiti users/groups and task (potential) assignees. We are using generic login to secure REST services and then simply assign tasks to the SSO (Google App Engine) user IDs even though there are no associated records in ACT_ID_USER, ACT_ID_GROUP or ACT_ID_MEMBERSHIP tables.


…………………………..