anonymous wrote : Less importantly, recursive evaluation causes resources to be tied up
unnecessarily. I've seen posts on this forum complaining about a "memory leak in
JBPM" - they perform a process loop a zillion times and watch the heap grow without
bound. This would be silly as a production scenario, but it's a very typical kind of
test to run.
This is 'fixed' in the PVM (upcomming core of jbpm 4.0) Koen gave Tom some good
spanking and in the meantime came up with a solution.
With regard to the discussion about exceptionhandlers or the 'failure
transitions', this is a hot topic in all processlanguages. I tried this once in a
small test example where the actionhandler on getting an exception, did not throw it, but
set a variable (which is possible if no exceptionhandlers are used). Transitions can be
'guarded' by expressions/conditions so the presence of a value in a certain
variable can make the process leave on a certain transition. This can be decided upon
designtime. On this leaving node you can e.g. use a compensating action that undo's
previous actions. Kind of complex though, but that is the case with all (afaik)
'languages' like bpel, ebbp, bpmn etc. Maybe Tom or Alex could comment on this as
well.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069715#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...