Hi, I've been using seam for a while now, but just started looking at the jBPM integration. When reading
Practical Jboss Seam Projects I came across a discussion about storing JPA(EJB3)entities in the process context.
The book says that there is two problems with this approach:
1) jBPM uses the hibernate xml mapping and can't use JPA annotations
2) if we write our own hibernate to jpa mapping there could still be problems
but this could be fairly risky, because we’re concurrently
running two persistence engines (our EJB 3.0 container and the Hibernate
runtime) against the same database tables, using the same Java objects.
Since the book came out in 2007 I was wondering if this is still the case? If so, is there any workarounds?
Yes, it is still the case. Jbpm still uses hibernate directly
Workaround? You could use your entites is you process context but they will be serialized to one field in jbpm database, or do what books says :)