[jBPM] - jBPM 5 console Process Overview Execution Details Diagram
by byungwoojun
byungwoojun [http://community.jboss.org/people/byungwoojun] created the discussion
"jBPM 5 console Process Overview Execution Details Diagram"
To view the discussion, visit: http://community.jboss.org/message/605911#605911
--------------------------------------------------------------
I am using jBPM 5. Using Eclipse BPMN Process designer, I created a process flow with a mesage event node and export it to Guvnor. I am using the KnowledgeAgent.applyChangeSet to get the resources from Guvnor. So far, so good.
The process flow ran successfully and returned when it hit the message event node, was waitng for a signalEvent. I logged in the jBPM 5 Console (jbpm-gwt-console) to see the running process. In the Process Overview, there was my process. I clicked its instance and clicked the Diagram buttion to see the diagram. Then, I got the following exception:
*org.drools.repository.RulesRepositoryException: javax.jcr.PathNotFoundException: com.company.auto.usecase5-image####*
*Caused By: javax.jcr.PathNotFoundException: com.company.auto.usecase5-image###*
The com.company.auto.usecase5 is a process pid. What is the "-image"?
Any suggestion will be appreciated.
Thanks,
bwj
<May 18, 2011 2:59:58 PM EDT> <Error> <HTTP> <BEA-101017> <[ServletContext@741498[app:drools-guvnor module:drools-guvnor.war path:/drools-guvnor spec-version:null]] Root cause of ServletException.
*org.drools.repository.RulesRepositoryException: javax.jcr.PathNotFoundException: com.company.auto.usecase5-image#######*#
at org.drools.repository.PackageItem.loadAsset(PackageItem.java:652)
at org.drools.guvnor.server.files.PackageDeploymentServlet$1.a(PackageDeploymentServlet.java:176)
at org.drools.guvnor.server.files.RepositoryServlet.doAuthorizedAction(RepositoryServlet.java:97)
at org.drools.guvnor.server.files.PackageDeploymentServlet.doGet(PackageDeploymentServlet.java:133)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:715)
Truncated. see log file for complete stacktrace#####
*Caused By: javax.jcr.PathNotFoundException: com.company.auto.usecase5-image######*#
at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2437)
at org.drools.repository.PackageItem.loadAsset(PackageItem.java:648)
at org.drools.guvnor.server.files.PackageDeploymentServlet$1.a(PackageDeploymentServlet.java:176)
at org.drools.guvnor.server.files.RepositoryServlet.doAuthorizedAction(RepositoryServlet.java:97)
at org.drools.guvnor.server.files.PackageDeploymentServlet.doGet(PackageDeploymentServlet.java:133)
Truncated. see log file for complete stacktrace
>
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605911#605911]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 1 month
[jBPM] - Different WorkItemManager objects
by Cristiano Nicolai
Cristiano Nicolai [http://community.jboss.org/people/cristiano.nicolai] created the discussion
"Different WorkItemManager objects"
To view the discussion, visit: http://community.jboss.org/message/605548#605548
--------------------------------------------------------------
Hi guys,
I'm playing with a JPA StatefulKnowledgeSession and just realized that the WorkItemManager instance received as parameter on my WorkItemHandler isn't the same object that I get when I call ksession.getWorkItemManager().
WorkItemHandler: org.drools.persistence.jpa.processinstance.JPAWorkItemManager@48dfaa07
ksession.getWorkItemManager(): org.drools.command.impl.CommandBasedStatefulKnowledgeSession$1@6de525a1
I understand that a CommandBasedStatefulKnowledgeSession uses a CommandService to encapsulate a single session and probably what I'm receiving on my handler is the manager associated to this session and not the one available on the CommandBasedStatefulKnowledgeSession.
I faced this situation because I tried to update the CommandBasedWSHumanTaskHandler to not depend on a KnowledgeSession and only use the WorkItemManager received as parameter, but then some problems started to happen.
Just want to understand if this should be considered as a normal behavior.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605548#605548]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 1 month