This content has been marked as final.
Show 4 replies
-
1. Re: Seam 2.0.CR1, jBPM and custom entity process variables
pmuir Dec 26, 2007 12:49 PM (in response to mschmidke)Do you still need help with this? Sorry, I lost track of the issue.
-
2. Re: Seam 2.0.CR1, jBPM and custom entity process variables
mschmidke Dec 26, 2007 3:07 PM (in response to mschmidke)"pete.muir@jboss.org" wrote:
Do you still need help with this? Sorry, I lost track of the issue.
Yes and no ...I get perfectly along when I do it without Seam's jBPM support, but of course this is a pity because I want to get the best out of Seam.
To abstract my problem:
When I began my project, I spent two or three days getting jBPM and EJB3 together such that I can reference EJB3 entity beans as jBPM process variables. This wasn't ready documented, but I managed it.
A few weeks later I tried to get Seam into this, but had no success, because Seam wasn't compatible to the way I injected my Persistence Context's Hibernate Session into jBPM (for that jBPM uses Persistence Context's transaction scope which is finally a Seam managed transaction).
I am not sure whether I am doing something wrong or whether this is a feature request.
Did you ever interweave jBPM and EJB3?
Happy Holidays,
Marcus. -
3. Re: Seam 2.0.CR1, jBPM and custom entity process variables
pmuir Dec 26, 2007 3:39 PM (in response to mschmidke)Normally when you use Seam with jbpm and want process variables you would use Seam's business process scope (which is not the same thing).
We haven't tried using process variables that are JPA entities with Seam, so I guess if you file a JIRA request with a runnable test case we can take a look... -
4. Re: Seam 2.0.CR1, jBPM and custom entity process variables
mschmidke Dec 26, 2007 4:22 PM (in response to mschmidke)"pete.muir@jboss.org" wrote:
Normally when you use Seam with jbpm and want process variables you would use Seam's business process scope (which is not the same thing).
Yes ... I really did not try this ... but I cannot imagine what the result would be ... I do not really like byte array process variables containing serialized data because we want to be able to look with third party software at the data.
I'll file an issue when I am back in office next week.
Marcus.