[JBoss JIRA] Created: (JBPM-2106) jpdl 3 feature coverage
by Tom Baeyens (JIRA)
jpdl 3 feature coverage
-----------------------
Key: JBPM-2106
URL: https://jira.jboss.org/jira/browse/JBPM-2106
Project: JBoss jBPM
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.0.0.GA
this issue lists features that were not prioritized in jpdl 4. for each feature, we should evaluate whether we actually want to include this to support migration. and if we do, whether this should be part of the user guide or of the developers guide (deprecate it)
* Advanced task properties:
<task subtask-synchronization="first, last, unsynchronized, never">
<task blocking="true">
* Assignment expression language
* Config types for user code
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBPM-2528) Behavior of tasks completion when inside two or more
by Romain LM (JIRA)
Behavior of tasks completion when inside two or more
----------------------------------------------------
Key: JBPM-2528
URL: https://jira.jboss.org/jira/browse/JBPM-2528
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: - jBPM Version : 4.1
- Database : MySQL 5.1
- JDK : 1.6.0_15
- Container : java -version
- Configuration : default jbpm.cfg.xml
- Libraries : default librairies
Reporter: Romain LM
I do not understand the behavior of tasks completion when they are inside two or more forks. You will find the accurate questions in the test case comments.
[code]
<?xml version="1.0" encoding="UTF-8"?>
<process key="test1" name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start name="start1">
<transition name="to fork1" to="fork1"/>
</start>
<fork name="fork1">
<transition name="to task1" to="task1"/>
<transition name="to task2" to="task2"/>
</fork>
<task name="task2">
<transition name="to join2" to="join2"/>
</task>
<task name="task1">
<transition name="to fork2" to="fork2"/>
</task>
<fork name="fork2">
<transition name="to task1.1" to="task1.1"/>
<transition name="to task1.2" to="task1.2"/>
</fork>
<taskname="task1.1">
<transition name="to join1" to="join1"/>
</task>
<task name="task1.2">
<transition name="to join1" to="join1"/>
</task>
<join name="join1">
<transition name="to join2" to="join2"/>
</join>
<join name="join2">
<transition name="to end1" to="end1"/>
</join>
<end name="end1"/>
</process>
[/code]
[code]
// test case which extends JbpmTestCase
public void testTaskConcurrency() {
repositoryService.createDeployment().addResourceFromClasspath("test1.jpdl.xml").deploy();
ProcessInstance processInstance = executionService.startProcessInstanceByKey("test1");
String processInstanceId = processInstance.getId();
System.out.println("Process started:");
for (Task taskTemp : taskService.createTaskQuery().processInstanceId(processInstanceId).list()) {
System.out.println(String.format("> Task '%s' with execution '%s'", taskTemp.getActivityName(), taskTemp.getExecutionId()));
}
/* Output (ok):
* > Task 'task1' with execution 'test1.1.to task1'
* > Task 'task2' with execution 'test1.1.to task2'
*/
Task task = taskService.createTaskQuery().processInstanceId(processInstanceId).activityName("task1").uniqueResult();
taskService.completeTask(task.getId());
System.out.println("task1 completed:");
for (Task taskTemp : taskService.createTaskQuery().processInstanceId(processInstanceId).list()) {
System.out.println(String.format("> Task '%s' with execution '%s'", taskTemp.getActivityName(), taskTemp.getExecutionId()));
}
/* Output (strange):
* > Task 'task2' with execution 'test1.1.to task2'
* > Task 'task1.1' with execution 'test1.1.to task1.1'
* > Task 'task1.2' with execution 'test1.1.to task1.2'
* > Task 'task1.1' with execution 'test1.1.to task1'
*/
/* Questions:
* Why do I have 2 different 'task1.1' (with different execution id)?
* Which one should I complete?
* Imagine task1 is not a task but a subprocess, this subprocess would be started twice. Is it norm
al?
*/
// I cannot use the uniqueResult() method (the task I want to get is not unique)
task = taskService.createTaskQuery().processInstanceId(processInstanceId).activityName("task1.1").list().get(0);
taskService.completeTask(task.getId());
System.out.println("task1.1 completed:");
for (Task taskTemp : taskService.createTaskQuery().processInstanceId(processInstanceId).list()) {
System.out.println(String.format("> Task '%s' with execution '%s'", taskTemp.getActivityName(), taskTemp.getExecutionId()));
}
/* Output (still strange):
* > Task 'task2' with execution 'test1.1.to task2'
* > Task 'task1.1' with execution 'test1.1.to task1.1'
* > Task 'task1.2' with execution 'test1.1.to task1.2'
*/
task = taskService.createTaskQuery().processInstanceId(processInstanceId).activityName("task1.2").uniqueResult();
taskService.completeTask(task.getId());
System.out.println("task1.2 completed:");
for (Task taskTemp : taskService.createTaskQuery().processInstanceId(processInstanceId).list()) {
System.out.println(String.format("> Task '%s' with execution '%s'", taskTemp.getActivityName(), taskTemp.getExecutionId()));
}
/* Output (still strange):
* > Task 'task2' with execution 'test1.1.to task2'
* > Task 'task1.1' with execution 'test1.1.to task1.1'
*/
/* Question:
* I reached the first join, why do I still see the second 'task1.1'?
*/
task = taskService.createTaskQuery().processInstanceId(processInstanceId).activityName("task2").uniqueResult();
taskService.completeTask(task.getId());
System.out.println("task2 completed:");
for (Task taskTemp : taskService.createTaskQuery().processInstanceId(processInstanceId).list()) {
System.out.println(String.format("> Task '%s' with execution '%s'", taskTemp.getActivityName(), taskTemp.getExecutionId()));
}
/* Output (ok):
* [nothing]
*/
}
[/code]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBPM-1934) Console API integration: Failed to retrieve token
by Heiko Braun (JIRA)
Console API integration: Failed to retrieve token
-------------------------------------------------
Key: JBPM-1934
URL: https://jira.jboss.org/jira/browse/JBPM-1934
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 Beta3
Caused by: java.lang.IllegalStateException: Cannot obtain associated token
at org.jbpm.integration.spec.task.TaskInstanceImpl.getCorrelationKey(TaskInstanceImpl.java:144)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jbpm.integration.spec.runtime.InvocationProxy.invoke(InvocationProxy.java:107)
at $Proxy101.getCorrelationKey(Unknown Source)
This does slip through the test coverage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBPM-1948) Report server config doesn't work across databases
by Heiko Braun (JIRA)
Report server config doesn't work across databases
--------------------------------------------------
Key: JBPM-1948
URL: https://jira.jboss.org/jira/browse/JBPM-1948
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 Beta3
"If your report design contains a JDBC data source defined with both JDBC Driver URL and JNDI name, then JNDI service will be used first and JDBC driver will be used as fallback. The username and password properties, if specified, are used in both cases. "
Even when using the datasource, BIRT reconfigures the credentials. That means you cannot simply point the JBPM datasource to a different database, which uses other credentials.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBPM-1950) webSale metrics problem
by Tom Baeyens (JIRA)
webSale metrics problem
-----------------------
Key: JBPM-1950
URL: https://jira.jboss.org/jira/browse/JBPM-1950
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: windows
jboss 5.0.0.GA
mysql
jbpm 3 build from trunk sources
Reporter: Tom Baeyens
Fix For: jBPM 3.3.1 GA
i deployed the websale example and started 2 executions with 'add'.
then i went to Process Metrics --> Process Workload. i selected process websale and clicked 'Examine'. Then I got an error in the content window:
The following items have errors:
ReportDesign (id = 1):
+ Column binding "startDate" has referred to a data set column "startDate" which does not exist.
data.engine.ColumnBindingReferToInexistColumn ( 3 time(s) )
detail : org.eclipse.birt.data.engine.core.DataException: Column binding "startDate" has referred to a data set column "startDate" which does not exist.
at org.eclipse.birt.data.engine.impl.ResultIterator.validateManualBindingExpressions(ResultIterator.java:272)
at org.eclipse.birt.data.engine.impl.ResultIterator.<init>(ResultIterator.java:145)
at org.eclipse.birt.data.engine.impl.QueryResults.getResultIterator(QueryResults.java:180)
at org.eclipse.birt.report.engine.data.dte.QueryResultSet.<init>(QueryResultSet.java:83)
at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:157)
at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:117)
at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:182)
at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1685)
at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:76)
at org.eclipse.birt.report.engine.executor.TableItemExecutor.execute(TableItemExecutor.java:61)
at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:42)
at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:45)
at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:33)
at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:63)
at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:85)
at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:106)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:140)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:68)
at org.jboss.balalaika.BirtService.render(BirtService.java:152)
at org.jboss.balalaika.ReportFacade.viewReportHtml(ReportFacade.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:77)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:197)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:185)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:123)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:348)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:182)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:90)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:66)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months