Hello Koen Thanks for replying about the jpdl alpha3 issues.
1. With respect to the presence of the jpeg (for monitoring), I have to make sure that the jpeg is being included in the deploy (of course) and what I had found is that unless I carefully "clean" the eclipse project, there was (only sometimes) some issue with this. So this is no longer an issue. 2. I will take your advice and try the jpdl alpha4. Which brings me to the current issue. I am running jpdl alpha3 in the jbpm-starters-kit-3.1.4 because I could not get the following signalling servlet to work with the jbpm-jpdl-suite-3.2.GA release. I am including the relevant code below. I looked at the 3.2.GA jbpm runtime lib javadocs and see nothing particularly obvious that would indicate that the code (which works fine in 3.1.4) is no longer compliant with 3.2.GA. | JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance(); | JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); | ProcessInstance processInstance = null; | try { | processInstance = jbpmContext.loadProcessInstance(processInstanceId); | etc., etc., ... | With the 3.2.GA runtime, there are a series of either classes or ...hbm.xml files that are not found. This problem does not exist when using the 3.1.4 runtime. Question: is there a new model for getting the ProcessInstance ? Maurice Yarrow SplashNote Systems Santa Clara, California View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043992#4043992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043992 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user