ok, so I dug a little deeper and it appears that there is no way to do this without replicating the entire identity/demographic data in the jbpm database. So in order to achieve this functionality and only have one set of data to manage, I see only two ways:
1. Drop the foreign key constraint that leads from the jbpm_pooledactor table to the jbpm_taskactorpool table. 2. Create a new table very similar to the jbpm_taskactorpool without a constraint to the jbpm_pooledactor table. This could be linked via a custom TaskInstance class. In both the above scenarios a foreign key will exist to link the task instance to the task actor pool, and each actor in the pool table will be stored alongside that foreign key. The only difference will be the lack of constraints to the identity model of jBPM (e.g. the jbpm_pooledactor table as constraint fk_tskactpol_plact). I presume to have this functionality without adopting the "optional" jBPM identity model, such a change will be required in the jBPM code. I look forward to any feedback, esp if anyone has an arguement for redundantly storing the identity model. Thanks again. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3945464#3945464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3945464 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
