I agree that you don't want to be using the jBPM tables in your domain, I'd encourage you to look at either writing converters OR switching to jBPM 3.1.
You can write converters in either version, allowing you to reference full domain objects in the process (including in scripts via the context) while storing said objects in your own domain tables. In 3.1 this is transparent and quite wonderful assuming your object is "hibernatable". That is, if the hibernate configuration tells the engine that it knows how to persist your type, you can use it as a variable in your process and jBPM via hibernate will handle persisting the object and loading it when you reference it. I'm pretty sure there are some boundaries related to the use of complex keys etc, but for most things with a "standard" single field primary key jBPM will handle this for you. That said, I'm not aware of this feature in 3.0 - please correct me if I'm wrong, but 3.0 IIRC wanted you to supply converters (tiny little things really), but 3.1 just makes things cleaner. Short of that - the standard jBPM<-> UI responses apply - write one :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967667#3967667 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967667 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
