anonymous wrote : "kukeltje" wrote : The fact that it is invoked (how do ypou
see that from this log btw...) does not mean the result is used.The fact that the message
is logged from the handler...
Yes, the handler is called, I see that. I meant that the 'result' isn't used.
anonymous wrote : "kukeltje" wrote : btw, why do you do a leave node in an
assignment handler? That is realy wrong.Hang-over from my early experiments with jBPM. I
think without it, although the process starts, it gets 'stuck' in the start
state.
Still then, it is realy wrong. And if you have a start task don't you want it to stay
in the start node???
anonymous wrote :
| All I was hoping for with this thread was to get some ideas as to why the
DelegationException is thrown when I invoke createStartTaskInstance() from a jUnit test,
but NOT when the same code is run as part of the normal running of the app.
That is new information (or maybe I missed it somewhere in the split posts). Most often it
is a classloader issue if you see this different behaviour
anonymous wrote : I had assumed that the range of possible causes for that exception had
probably been experienced by someone. I'm still hoping that someone will give me some
guesses or suggestions for investigation.
That is why a real unittest is handy for *us* so we can try to replicate the issue
locally...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194819#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...