[JBoss jBPM] - Error in compositeLog
by helidesai
Hello,
I am using JBPM 3.1.2. I am trying to save process instance and then retireve it from database. My code is in message driven bean, so whenever I receive message , the bean activates the process. When I try to retrieve the process instance and run processInstance.signal(), I am getting NullPointerException at org.jbpm.graph.exe.Token.startCompositeLog. Do I need to do some loggigin for this? I have seen the database example given in the tutorial, but nothing abt logging is mentioned in it.
This is the process which retrieves the processInstance from the database.
public void resumeProcess(){
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try{
GraphSession graphSession = jbpmContext.getGraphSession();
ProcessDefinition processDefinition =
graphSession.findLatestProcessDefinition("NOCProcess1");
List processInstances =
graphSession.findProcessInstances(processDefinition.getId());
ProcessInstance processInstance =
(ProcessInstance) processInstances.get(0);
processInstance.signal();
jbpmContext.save(processInstance);
}catch(Exception e)
{
e.printStackTrace();
}finally {
jbpmContext.close();
}
}
Please help me.
Regards,
Heli.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970935#3970935
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970935
19 years, 7 months
[JBossWS] - JSR-109 service endpoint and EJB3
by be324854
I know that an EJB3 Stateless sessions beans that doubles as a web service endpoints should be annotated according to the JSR-181 standard. But since JBossWS 1.x does not support related standards like JAX-B 2.0 (e.g. namespace of the elements) and JAX-WS 2.0 (e.g the Exception structure). That makes it pretty useless for a production environment.
Since the project I will work on will go into staging before the probable release date of JBossWS 2.x I was thinking of a different approach. The O?Reilly book ?Enterprise JavaBeans 3.0? indicates that JAX-RPC 1.1 is still appropriate for EJB3, and I wanted to use that since JBossWS 1.x has good support for that.
I see in the deployment code that ?JSR109_EJB3? not exists. Does that mean that I can?t expose EJB3 Stateless session beans as a web services via the JSR-109 standard? If not can it be added in the near future?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970931#3970931
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970931
19 years, 7 months