[JBoss JIRA] Created: (JBPM-2755) EL support in task
by henry donnell (JIRA)
EL support in task
-------------------
Key: JBPM-2755
URL: https://jira.jboss.org/jira/browse/JBPM-2755
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.4
Reporter: henry donnell
Fix For: jBPM 4.4
it would be helpful to be able to use EL in the <description> tag of the (human) task node.
This will allow to create dynamical task descriptions based on the process variables.
Example:
<task name="review_task">
<description>Review order nr.#{order.nr} from customer #{order.customer.name}</description>
</task>
The main purpose is to make human task descriptions in the task list more readable and user-friendly.
Because if you have 20 task instances of the same task and they are all called "Review order from customer" it is really hard to see at a first glance which task is related to which customer.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2642) A patch to support DB2 on zOS
by Richard L. Burton III (JIRA)
A patch to support DB2 on zOS
-----------------------------
Key: JBPM-2642
URL: https://jira.jboss.org/jira/browse/JBPM-2642
Project: jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.8, jBPM 3.2.7
Environment: Java version: 1.6.0_16,Sun Microsystems Inc., OS-System: Windows XP 5.1,x86, jboss-soa-p.4.3.0, DB2, version: DSN09015, Hibernate 3.2.4.sp1.cp08
Reporter: Richard L. Burton III
Priority: Blocker
Attachments: findJobsWithOverdueLockTime.patch
When using jBPM with DB2 on zOS the JobSession object throws an exception when trying to find jobs with overdue lock time. The exception thrown is:
DB2 SQL error: SQLCODE: -180, SQLSTATE: 22007, SQLERRMC: 1
I attached a patch which corrects this problem. Currently JobSession#findJobsWithOverdueLockTime(Date) is using Query#setDate(..) instead of Query#setTimestamp(...)
This isn't a problem when using the DB2 Universal version on windows, only on zOS.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-1139) The ClassUtil class is not thread-safe
by Wojciech Gdela (JIRA)
The ClassUtil class is not thread-safe
--------------------------------------
Key: JBPM-1139
URL: http://jira.jboss.com/jira/browse/JBPM-1139
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.3
Reporter: Wojciech Gdela
Assigned To: Tom Baeyens
Attachments: ClassUtil-concurrency-issue.zip
The ClassUtil class is not thread-safe. The exception will occur when two thread simultanously try do deserialize variables from two different process definitions. Look at the code:
{code}
public ContextObjectInputStream(final InputStream in,
ProcessInstance processInstance) throws IOException {
super(in);
this.setProcessInstance(processInstance);
ClassUtil.setProcessInstance(processInstance);
}
...
protected Class resolveClass(final ObjectStreamClass desc)
throws IOException, ClassNotFoundException {
return ClassUtil.forName(desc.getName(), ContextObjectInputStream.class);
}
...
ContextObjectInputStream cois = new ContextObjectInputStream(bais, definition.createProcessInstance());
// when here another thread tries to execute the same code with another process instance there will be a problem
return cois.readObject();
{/code}
Further description of issue is in attached test case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2591) Simulation module has transitive dependency on commons-beanutils
by Alejandro Guizar (JIRA)
Simulation module has transitive dependency on commons-beanutils
----------------------------------------------------------------
Key: JBPM-2591
URL: https://jira.jboss.org/jira/browse/JBPM-2591
Project: jBPM
Issue Type: Task
Components: Runtime Engine
Affects Versions: jBPM 3.2.8
Environment: hsqldb
java14
linux
Reporter: Alejandro Guizar
Priority: Minor
Fix For: jBPM 3.2.x
A recent CI build failed due to:
[INFO] Compilation failure
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[10,36] package org.apache.commons.beanutils does not exist
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[607,8] cannot find symbol
symbol : variable PropertyUtils
location: class org.jbpm.sim.def.JbpmSimulationModel
/qa/hudson_ws/workspace/jbpm3-jboss405/database/hsqldb/jdk/java14/label/linux/jbpm/modules/simulation/src/main/java/org/jbpm/sim/def/JbpmSimulationModel.java:[609,23] cannot find symbol
symbol : variable PropertyUtils
location: class org.jbpm.sim.def.JbpmSimulationModel
jbpm-simulation depends on jasperreports which in turn depends on commons-beanutils. Yet jbpm-simulation uses commons-beanutils directly, and should not rely on jasperreports' dependencies.
--
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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2703) Deserialization fails to work using custom Classloader
by Nicolas Leroux (JIRA)
Deserialization fails to work using custom Classloader
------------------------------------------------------
Key: JBPM-2703
URL: https://jira.jboss.org/jira/browse/JBPM-2703
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.2
Reporter: Nicolas Leroux
Fix For: jBPM 4.x
I am trying to use jBPM outside a servlet container and when storing a variable in the execution context, retrieving it I have:
Caught: java.lang.ClassNotFoundException: Blah
This is the same bug as described in:
http://jira.codehaus.org/browse/GROOVY-1627 . I think this is the following issue as well: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4340158 .
{quote}Java uses the last defined ClassLoader to loader the class. In many environments this might mean that the wrong class loader is chosen or that it works one day and the other day not. {quote}
The following code fixes the problem (in org.jbpm.pvm.internal.type.converter.SerializableToBytesConverter line 71 in the revert method:
{code}
ObjectInputStream ois = new ObjectInputStream(bais) {
protected Class resolveClass(ObjectStreamClass objectStreamClass) throws IOException, ClassNotFoundException {
return Class.forName(objectStreamClass.getName(), true, Thread.currentThread().getContextClassLoader());
}
};
{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
14 years, 7 months
[JBoss JIRA] Created: (JBPM-2844) Custom Mail Producer does not set the MailTemplate
by Telmo Simoes (JIRA)
Custom Mail Producer does not set the MailTemplate
--------------------------------------------------
Key: JBPM-2844
URL: https://jira.jboss.org/jira/browse/JBPM-2844
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Telmo Simoes
Priority: Critical
Fix For: jBPM 4.x
When using a custom email producer, the JpdlParser doesn't seem to set the MailTemplate. The following snippet was taken from the projects SVN (http://anonsvn.jboss.org/repos/jbpm/jbpm4/trunk/modules/jpdl/src/main/jav...)
---------------------------------------------------------------------------------------------------------------------------------------
public MailProducer parseMailProducer(Element element, Parse parse, String defaultTemplateName) {
// check whether the element is a generic object descriptor
if (ObjectBinding.isObjectDescriptor(element)) {
// TODO test custom mail producer
ObjectDescriptor objectDescriptor = parseObjectDescriptor(element, parse);
return (MailProducer) WireContext.create(objectDescriptor);
}
// parse the default producer
MailProducerImpl mailProducer = new MailProducerImpl();
mailProducer.setTemplate(parseMailTemplate(element, parse, defaultTemplateName));
return mailProducer;
}
---------------------------------------------------------------------------------------------------------------------------------------
I believe that when the condition "ObjectBinding.isObjectDescriptor(element)" is verified, the MailTemplate should be set before returning the MailProducer. This is performed when the default email producer is choosen.
--
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
14 years, 8 months