"gavin.king(a)jboss.com" wrote : If you want the jBPM+Seam integration to improve,
then you have to tell us exactly *what* limitations you are running into. I currently have
only 9 open business process related issues in JIRA, most of which are definitely
extremely minor, and only one of which came from a user (you).
|
| In fact, apart from the well-known limitation with respect to jBPM timers and
asynchronous events (which is slated for fixing in 1.3), I am not aware of *any* major
limitation to the Seam jBPM integration.
|
| I'm not claiming that there are no such limitations, merely that I don't know
what they are.
|
| If you are regularly resorting to writing jBPM custom actions/decision/assignment
handlers, then I need to know why that is and what feature it is that we are not providing
for. This is the first time I have heard that from anyone!
|
Go easy on me ;-) I just went through a lot of pain because of a deadline and our
internal collective inexperience with JBoss. Seriously though - it may be that we
didn't use jBPM as elegantly as we could have and I posted several questions here and
in the jBPM forum. I also got stuck in a situation where some code I inherited, a jBPM
ActionHandler, used Seam's ComponentgetInstance(...) to look up a SFSB and/or SLSB and
invoke a method. In this case, we were regularly having issues with Seam trying to close
managed resources - NO TRANSACTION exceptions. I couldn't find any decent
documentation, examples, or discussions around such a use case. So it's not
surprising if, as a user of Seam + jBPM, I don't have a glowing review.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029864#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...