[JBoss JIRA] Created: (JBPM-2958) Timer should refer to the business calendar used at the time of creation
by Toshiya Kobayashi (JIRA)
Timer should refer to the business calendar used at the time of creation
------------------------------------------------------------------------
Key: JBPM-2958
URL: https://jira.jboss.org/browse/JBPM-2958
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Toshiya Kobayashi
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Assuming you want to use different business calendars by loading different jbpm.cfg.xmls;
When you use a Timer, a scheduler service thread will set repeatDate to the timer using BusinessCalendar which is associated with given jbpmContext. The jbpmContext comes from default jbpm.cfg.xml (jbpm.esb/jbpm.cfg.xml). Also the BusinessCalendar field is static. So you cannot switch business calendars for each Timer in the scheduler service thread.
The timer should be able to acquire the business calendar which was used at the time of Timer creation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBPM-2834) Conditional transition cannot be considered as a default one
by Martin Vecera (JIRA)
Conditional transition cannot be considered as a default one
------------------------------------------------------------
Key: JBPM-2834
URL: https://jira.jboss.org/jira/browse/JBPM-2834
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8, jBPM 3.2.9
Environment: SOA-P 4.3.CP03 ER1
Reporter: Martin Vecera
The documentation reads:
====
The contents of the condition element is a jPDL expression that should evaluate to a boolean. A decision takes the first transition (as ordered in the processdefinition.xml) for which the expression resolves to true. If none of the conditions resolve to true, the default leaving transition (== the first one) will be taken.
====
If I have only a conditional transition in a node (hence the first one) it is not used as the default leaving transition.
Process definition to simulate the behaviour:
====
<?xml version="1.0" encoding="UTF-8"?>
<process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="processDefinition3">
<start-state name="start">
<transition to="node1"></transition>
</start-state>
<node name="node1" async="true">
<transition to="node2" condition="#{AAA == null}"></transition>
</node>
<node name="node2">
<transition to="end1"></transition>
</node>
<end-state name="end1"></end-state>
</process-definition>
====
Exception being thrown on signaling process's token:
10:16:33,629 ERROR [JobExecutorThread] job execution failure
org.jbpm.JbpmException: transition is null
at org.jbpm.graph.def.Node.leave(Node.java:449)
at org.jbpm.graph.def.Node.leave(Node.java:430)
at org.jbpm.graph.def.Node.execute(Node.java:421)
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:597)
at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173)
at org.jbpm.graph.def.Node_$$_javassist_81.execute(Node_$$_javassist_81.java)
at org.jbpm.job.ExecuteNodeJob.execute(ExecuteNodeJob.java:24)
at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:192)
at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:66)
JBPM-Console says:
Error signalling token: An exception of type "org.jbpm.JbpmException" was thrown. The message is: Node(node1) has no default transition
--
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
13 years, 10 months
[JBoss JIRA] Created: (JBPM-3028) "Full" installer
by Kris Verlaenen (JIRA)
"Full" installer
----------------
Key: JBPM-3028
URL: https://issues.jboss.org/browse/JBPM-3028
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Kris Verlaenen
Assignee: Kris Verlaenen
Fix For: jBPM 5.0
Create an installer zip that already contains part of the artefacts that would otherwise have to be downloaded, as people apparently can't wait for a little while until dependencies are downloaded ;)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBPM-3022) Update wiki to include architectural overview of jBPM5
by Eric D. Schabell (JIRA)
Update wiki to include architectural overview of jBPM5
------------------------------------------------------
Key: JBPM-3022
URL: https://issues.jboss.org/browse/JBPM-3022
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: jBPM 5.0 CR1
Reporter: Eric D. Schabell
Priority: Minor
Fix For: jBPM 5.0
>From the forums: http://community.jboss.org/message/582241
There was a very interesting post nearly a year ago about the new jBPM5 project. It included some architectural overview and description of components, etc. http://community.jboss.org/wiki/jBPM5RequestforComments
I was wondering how much of this is going to be realised in the first release of jBPM5 (it looks like a lot of it will be in jBPM5). It would be great to get an updated version of something like this overview that reflects exactly what will be in the first release and how it will all fit together.
Perhaps this could be a good first candidate for a jBPM wiki update. It is time that there was a "jBPM 5" heading in the wiki!
Of course the more detail the better at this level particularly for those like me who are trying to get their head around how jBPM can be integrated into their environment.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBPM-3029) JBPM runtime throws error while executing Action task with MVLE Dialect
by shashi mhatre (JIRA)
JBPM runtime throws error while executing Action task with MVLE Dialect
-----------------------------------------------------------------------
Key: JBPM-3029
URL: https://issues.jboss.org/browse/JBPM-3029
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 5.0
Environment: eclipse 3.6, windows xp, jdk 1.6, runtime - jbpm 5.0 Snapshot build#70
Reporter: shashi mhatre
JBPM runtime throws below error while executing action task with MVLE dialect.
java.lang.RuntimeException: unable to execute Action
at org.jbpm.workflow.instance.node.ActionNodeInstance.internalTrigger(ActionNodeInstance.java:49)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:122)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:185)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:150)
at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49)
at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:122)
at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35)
at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:188)
at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:302)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:124)
at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:105)
at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1094)
at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:297)
at com.sample.ProcessTest.main(ProcessTest.java:48)
Caused by: java.lang.ClassCastException: org.mvel2.compiler.ExecutableAccessor cannot be cast to org.mvel2.compiler.CompiledExpression
at org.jbpm.process.instance.impl.MVELAction.execute(MVELAction.java:117)
at org.jbpm.workflow.instance.node.ActionNodeInstance.internalTrigger(ActionNodeInstance.java:47)
... 14 more
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months