[jbpm-dev] [Design of JBoss jBPM] - Re: login 'unification'

kukeltje do-not-reply at jboss.com
Wed Jul 30 06:08:38 EDT 2008


Heiko,

Sorry for the kind of rude tone in my comment in Jira, but there are so many changes and things going one without (at least for what it seems public) discussion that it is very hard to follow things and still have a clear overall picture. I sometimes get the impression that people making changes also have no clear picture, a clear picture of jBPM that is. The fact that you ask what the relation is with the identity module to me is an example of this (no offence). Changes like this login config lead to unnecessary discussions, frustrations if changes are discussed upfront.

Ok, now the elaboration.

The identity module  can be used to do assignments in the workflow engine. There is a kind of 'expression language' that can be used to decide e.g. who should get a task. The default implementation of this uses the database with users, groups, role etc... so when part of this is in files, we either have to duplicate things, keep them in sync or rewrite the identity module to use files (nah... ). The login-config.xml currently uses the same database as identity module, so things are shared and *unified*. 

Using the database instead of files would solve this, so keeping things as they are... regardless of using a .sar for this.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167565#4167565

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167565



More information about the jbpm-dev mailing list