for the record: i wasn't spanking you. (at least not this time:-) i added that to
the docs because you pointed out a hole in the docs. thanks !
anonymous wrote : But still, this doesn't lead to a problem with the getActivityName,
or? If I am in a composite, the root execution may be in the scope/composite state, and
the child in the "real" state.
exactly. the parent execution will have as execution state
Execution.STATE_INACTIVE_CONCURRENT_ROOT and it should still point to the scope/composite
activity. the leaves point to the real activity.
the difference with before is that each activity that has variables or timers declared on
it, will also create a child token. the parent execution will be in state
STATE_INACTIVE_SCOPE and the (single) child will be in state STATE_ACTIVE_ROOT
in that case the parent execution will be in state
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242883#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...