[jBPM] - Re: Integrating TaskService with jbpm-console
by roxy1987
roxy1987 [https://community.jboss.org/people/roxy1987] created the discussion
"Re: Integrating TaskService with jbpm-console"
To view the discussion, visit: https://community.jboss.org/message/785124#785124
--------------------------------------------------------------
Hi Bpmn2user,
It has been quite some time since you posted this.
I tried using the servlet you attached above to get rid of human task service related stuff. It could not connect to the task client. Below is the trace. COuld you please take a look at it and lemme know what I might have done wrong.
* URL: ' http://localhost:8080/gwt-console-server/rs/tasks/krisv http://localhost:8080/gwt-console-server/rs/tasks/krisv'
* Action: 'org.jboss.bpm.console.client.task.LoadTasksAction'
* Exception: 'class com.google.gwt.http.client.RequestException'
HTTP 500:
h1. HTTP Status 500 - java.lang.IllegalArgumentException: Could not connect task client
----
*type* Exception report
*message* java.lang.IllegalArgumentException: Could not connect task client
*description* The server encountered an internal error that prevented it from fulfilling this request.
*exception*
org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Could not connect task client
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
*root cause*
java.lang.IllegalArgumentException: Could not connect task client
org.jbpm.integration.console.TaskManagement.connect(TaskManagement.java:66)
org.jbpm.integration.console.TaskManagement.getAssignedTasks(TaskManagement.java:179)
org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
*note* The full stack trace of the root cause is available in the Apache Tomcat/6.0.36 logs.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/785124#785124]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - Failed to read schema document
by Danilo Rizzo
Danilo Rizzo [https://community.jboss.org/people/drjbpm] created the discussion
"Failed to read schema document"
To view the discussion, visit: https://community.jboss.org/message/784580#784580
--------------------------------------------------------------
Hello All,
I created a process in guvnor with JBPM Designer 2.4.0.
When I try to execute it, I get the following warning.
(null: 8, 96): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 17, 79): src-resolve: Cannot resolve the name 'bpmndi:BPMNDiagram' to a(n) 'element declaration' component.
(null: 20, 52): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 20, 52): cvc-complex-type.2.4.a: Invalid content was found starting with element 'bpmndi:BPMNDiagram'. One of '{" http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg.org/spec/BPMN/20100524/MODEL":rootElement, " http://www.omg.org/spec/BPMN/20100524/MODEL http://www.omg.org/spec/BPMN/20100524/MODEL":relationship}' is expected.
(null: 21, 76): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 22, 106): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 23, 68): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 25, 106): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 26, 69): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 28, 185): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 29, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 29, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 29, 63): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 30, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 30, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 30, 63): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 32, 106): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 33, 68): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 35, 185): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/BPMN/20100524/DI-XMI http://www.omg.org/spec/BPMN/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 36, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 36, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 36, 63): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 37, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DI-XMI http://www.omg.org/spec/DD/20100524/DI-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 37, 63): schema_reference.4: Failed to read schema document ' http://www.omg.org/spec/DD/20100524/DC-XMI http://www.omg.org/spec/DD/20100524/DC-XMI', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
(null: 37, 63): cvc-elt.4.2: Cannot resolve 'dc:Point' to a type definition for element 'di:waypoint'.
(null: 41, 52): cvc-complex-type.4: Attribute 'type' must appear on element 'bpmn2:relationship'.
(null: 44, 92): cvc-elt.4.2: Cannot resolve 'drools:Scenario' to a type definition for element 'drools:Scenario'.
(null: 47, 69): cvc-elt.4.2: Cannot resolve 'drools:TimeParameters' to a type definition for element 'drools:TimeParameters'.
(null: 48, 66): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:ProcessingTime'.
(null: 53, 69): cvc-elt.4.2: Cannot resolve 'drools:CostParameters' to a type definition for element 'drools:CostParameters'.
(null: 54, 60): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:UnitCost'.
(null: 60, 75): cvc-elt.4.2: Cannot resolve 'drools:ControlParameters' to a type definition for element 'drools:ControlParameters'.
(null: 61, 63): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:Probability'.
(null: 67, 69): cvc-elt.4.2: Cannot resolve 'drools:TimeParameters' to a type definition for element 'drools:TimeParameters'.
(null: 68, 66): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:ProcessingTime'.
(null: 75, 69): cvc-elt.4.2: Cannot resolve 'drools:TimeParameters' to a type definition for element 'drools:TimeParameters'.
(null: 76, 60): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:WaitTime'.
(null: 83, 75): cvc-elt.4.2: Cannot resolve 'drools:ControlParameters' to a type definition for element 'drools:ControlParameters'.
(null: 84, 63): cvc-elt.4.2: Cannot resolve 'drools:Parameter' to a type definition for element 'drools:Probability'.
Hello World!
Any idea?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/784580#784580]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - No Persistence provider for EntityManager named org.jbpm.task
by Laura delli Paoli
Laura delli Paoli [https://community.jboss.org/people/lauradp] created the discussion
"No Persistence provider for EntityManager named org.jbpm.task"
To view the discussion, visit: https://community.jboss.org/message/785089#785089
--------------------------------------------------------------
Hello!
I'm trying to make my process data persistent and when I run
| EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.jbpm.task", properties); |
|
|
I get this error:
*No Persistence provider for EntityManager named org.jbpm.task*
*I'm starting my process in this way*
| EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.jbpm.task", properties); |
|
|
EntityManagerFactory emf = Persistence.createEntityManagerFactory("org.jbpm.task", properties);
KnowledgeSessionConfiguration config = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(properties);
Environment env = KnowledgeBaseFactory.newEnvironment();
env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
env.set(EnvironmentName.GLOBALS, new MapGlobalResolver());
StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(kbase, null, env);
ksession.startProcess("my_process", params);
See my persistence.xml attached.
Can anyone help me??
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/785089#785089]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - How to make jBPM process data persistent
by Laura delli Paoli
Laura delli Paoli [https://community.jboss.org/people/lauradp] created the discussion
"How to make jBPM process data persistent"
To view the discussion, visit: https://community.jboss.org/message/784551#784551
--------------------------------------------------------------
Hello everybody,
I need to store jBPM process data into my MySql database.
I was able to have Human Task data stored in Task table, but no information about processes is written on the database.
How can I solve this problem?
*Here's my persistence.xml:*
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<persistence version="2.0"
xmlns=" http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="org.jbpm.task">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:/jdbc/jbpm-ds</jta-data-source>
<mapping-file>META-INF/JBPMorm.xml</mapping-file>
<mapping-file>META-INF/Taskorm.xml</mapping-file>
<mapping-file>META-INF/ProcessInstanceInfo.hbm.xml</mapping-file>
<class>org.drools.persistence.info.SessionInfo</class>
<class>org.drools.persistence.info.WorkItemInfo</class>
<class>org.jbpm.persistence.processinstance.ProcessInstanceInfo</class>
<class>org.jbpm.process.audit.ProcessInstanceLog</class>
<class>org.jbpm.process.audit.NodeInstanceLog</class>
<class>org.jbpm.process.audit.VariableInstanceLog</class>
<class>org.jbpm.task.Attachment</class>
<class>org.jbpm.task.Content</class>
<class>org.jbpm.task.BooleanExpression</class>
<class>org.jbpm.task.Comment</class>
<class>org.jbpm.task.Deadline</class>
<class>org.jbpm.task.Comment</class>
<class>org.jbpm.task.Deadline</class>
<class>org.jbpm.task.Delegation</class>
<class>org.jbpm.task.Escalation</class>
<class>org.jbpm.task.Group</class>
<class>org.jbpm.task.I18NText</class>
<class>org.jbpm.task.Notification</class>
<class>org.jbpm.task.EmailNotification</class>
<class>org.jbpm.task.EmailNotificationHeader</class>
<class>org.jbpm.task.PeopleAssignments</class>
<class>org.jbpm.task.Reassignment</class>
<class>org.jbpm.task.Status</class>
<class>org.jbpm.task.Task</class>
<class>org.jbpm.task.TaskData</class>
<class>org.jbpm.task.SubTasksStrategy</class>
<class>org.jbpm.task.OnParentAbortAllSubTasksEndStrategy</class>
<class>org.jbpm.task.OnAllSubTasksEndParentEndStrategy</class>
<class>org.jbpm.task.User</class>
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.max_fetch_depth" value="3"/>
<property name="hibernate.hbm2ddl.auto" value="update" />
<property name="hibernate.show_sql" value="false" />
<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup" />
<!-- BZ 841786: AS7/EAP 6/Hib 4 uses new (sequence) generators which seem to cause problems -->
<property name="hibernate.id.new_generator_mappings" value="false" />
</properties>
</persistence-unit>
</persistence>
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/784551#784551]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
[jBPM] - Jbpm5.4 how to get task list from task server
by xin sun
xin sun [https://community.jboss.org/people/xs06974] created the discussion
"Jbpm5.4 how to get task list from task server"
To view the discussion, visit: https://community.jboss.org/message/785056#785056
--------------------------------------------------------------
HI guys, I am new to jbpm. I am using jbpm 5.4 following the jbpm-installer and I am thinking how to integrate the process system into my web application. One step is I wrote below code to query the task list for a user with userId.
The taskservice I used is the default one installed and deployed by the installer: jbpm-human-task-war.war, and I did no change any configuration file after the installation. I can query the task list from the eclipse *Human task view* successfully. But when I ran below code to query the task list for krisv(I am sure that I can get krisv's task from the Huamn task view), it always failed due to timeout, or just return 0:
//----------------------------------------------------------------------------------------------------------
import java.util.List;
import org.jbpm.task.AsyncTaskService;
import org.jbpm.task.service.hornetq.AsyncHornetQTaskClient;
import org.jbpm.task.service.responsehandlers.BlockingTaskSummaryResponseHandler;
public class TestTaskClient {
public static void main(String[] args) {
AsyncTaskService client = new AsyncHornetQTaskClient();
client.connect("127.0.0.1", 5153);
System.out.println("Good");
BlockingTaskSummaryResponseHandler taskSummaryHandler = new BlockingTaskSummaryResponseHandler();
client.getTasksAssignedAsPotentialOwner("krisv", "en-UK", taskSummaryHandler);
// I also tried client.getTasksAssignedAsPotentialOwner("krisv", null, taskSummaryHandler); but still failed;
List tasks = taskSummaryHandler.getResults();
}
}
//----------------------------------------------------------------------------------------------------------
Anyone tell me why? Thanks in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/785056#785056]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 3 months
