The problem is fixed!
It was caused by an programming error and had nothing to do with the JBPM framework. My
humble appologies to the people who spend time on this.
We are new to JBPM so we make some mistakes now and then :-))
Jan
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197538#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...