[JBoss JIRA] Created: (JBPM-3064) Use TemplateLoader to load ftl templates
by Cristiano Nicolai (JIRA)
Use TemplateLoader to load ftl templates
----------------------------------------
Key: JBPM-3064
URL: https://issues.jboss.org/browse/JBPM-3064
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JBossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
Attachments: 0006-Template-loading-refactoring.patch
Freemarker provides a mechanism to load templates from different sources named Template Loaders. Basically can be used URLTemplateLoader and ClassTemplateLoader to achieve the same behaviour provided in AbstractFormDispatcher but it gives an important feature to make possible to import different templates. For example:
<#import "common_task.ftl" as common/>
<@common.tasktemplate/>
This feature improve template reusability and use of generic macros.
Some other features can be achieved as template caching.
--
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-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-3049) JPAWorkingMemoryDbLogger.updateProcessLog uses hard coded query (likely hibernate specific)
by Jürgen Schmied (JIRA)
JPAWorkingMemoryDbLogger.updateProcessLog uses hard coded query (likely hibernate specific)
-------------------------------------------------------------------------------------------
Key: JBPM-3049
URL: https://issues.jboss.org/browse/JBPM-3049
Project: jBPM
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 5.2
Environment: OPENEJB 3.2, OPENJPA 2.0.1
Reporter: Jürgen Schmied
Assignee: Kris Verlaenen
in this function there is a hardcoded query string :
List<ProcessInstanceLog> result = getEntityManager().createQuery(
"from ProcessInstanceLog as log where log.processInstanceId = ? and log.end is null")
.setParameter(1, processInstanceId).getResultList();
it gives the following error:
<openjpa-2.0.1-r422266:989424 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: "Encountered "from" at character 1, but expected: ["DELETE", "SELECT", "UPDATE"]." while parsing JPQL "from ProcessInstanceLog as log where log.processInstanceId = ? and log.end is null". See nested stack trace for original parse error.
Fix: use a named query and put it in orm.xml
--
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-3052) jBPM Console is caching process instances after terminating it
by Cristiano Nicolai (JIRA)
jBPM Console is caching process instances after terminating it
--------------------------------------------------------------
Key: JBPM-3052
URL: https://issues.jboss.org/browse/JBPM-3052
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JBossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
When a process instance is terminated on jBPM Console, it remains on the listing.
Executing some testing, looks like Hibenate is caching the ProcessInstanceLog and keep returning it with end_date equals to null.
As may be useful for other circumstances, JPAProcessInstanceDbLog should offer a method to query active process.
Patch attached.
--
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-3051) Change jbpm-gwt-console-server to use only JPA as persistence mechanism
by Cristiano Nicolai (JIRA)
Change jbpm-gwt-console-server to use only JPA as persistence mechanism
-----------------------------------------------------------------------
Key: JBPM-3051
URL: https://issues.jboss.org/browse/JBPM-3051
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
Currently jbpm-gwt-console-server is using Hibernate and JPA to manage persistence information. Forcing to have two different configuration files (hibernate.cfg.xml and persistence.xml) and API's to use.
This request is to unify the data access through JPA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months