In general, I support what David and Ronald are saying. In order to get a clean,
performant association between our processes and business objects (ie, orders) we're
storing process instance ids in a dedicated table that maps to the business keys of our
business objects. Our process variable table is huge and we need something much smaller
that is properly indexed for speed.
Of course, if jBPM implemented a general business key, it would also need to support
configuration in the process def or what it should be called. Otherwise, different kinds
of keys (order/trouble ticket) could duplicate values, and a generic UI wouldn't know
what to call the key. (can't rely on process definition id or name to distinguish your
business key types, because a single business concept, like order, may be represented by
more than one process def depending on the kind of order). For performance, the business
key type should be stored directly against the key's value and procInstId, whether it
be a reference to the type string or the string itself.
-Britt
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017157#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...