well... could be just a bug in jBPM then. Please file a jira issue and well see.
But if you can find the real cause so the workaround mentioned in the other topic is not
needed any more would be even better :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121935#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...