coming back from a visit to brussels together with jeff delong, i realized the problem is
the different transaction strategies is the problem:
* in a ee environment, i want jbpm to be configured for JTA. i don't want the web
console to require EJB's. so we need some kind of abstraction between the web console
and the ejb's that manage the transactions. that is the command service pattern.
* the problem is that in a POJO environment we can easily manage the transactions
ourselves: one transaction for the updates, and after that one transaction for preparing
all the data for the new view.
I don't yet see how we can get a good transaction strategy that works on both
platforms... unless we can manage JTA transactions from inside the JSF backed beans.
i'll investigate a bit further and report if i find something that could mean a
solution. i just wanted to keep you up to date on where i just found that the command
service based interface between web console and jbpm has problems.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967568#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...