[JBoss JIRA] Created: (JBPM-1423) idenitfy supported deployments
by Tom Baeyens (JIRA)
idenitfy supported deployments
------------------------------
Key: JBPM-1423
URL: https://jira.jboss.org/jira/browse/JBPM-1423
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Priority: Critical
Identify the supported deployment environments and the corresponding configurations.
This basically will come down to transaction configurations in pvm, hibernate, spring, ejb and the likes.
Configurations:
* pvm
* hibernate
* ejb
Controlling transactions:
* Hibernate transaction programmatic
* Direct JDBC connection programmatic
* JTA UserTransaction programmatic (== BMT?)
* CMT through EJB deployment descriptors
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2717) "org.jbpm.pvm.internal.wire.WireException: couldn't initialize object 'null': couldn't find property setter setXXX for value true" for native boolean setters
by Per Christian Henden (JIRA)
"org.jbpm.pvm.internal.wire.WireException: couldn't initialize object 'null': couldn't find property setter setXXX for value true" for native boolean setters
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBPM-2717
URL: https://jira.jboss.org/jira/browse/JBPM-2717
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.3
Environment: Windows Vista, java 1.6, jboss 4.2.2.GA
Reporter: Per Christian Henden
I ran into a problem with accessing boolean properties of an eventListener.
I've attached a patch to trunk of ./modules/pvm/src/test/java/org/jbpm/pvm/internal/wire/ObjectWireTest.java that adds a test that exposes this problem.
Basically, the example below fails with the error
"org.jbpm.pvm.internal.wire.WireException: couldn't initialize object 'null': couldn't find property setter setCreateXml for value true"
JPDL-fragment:
<event-listener expr="#{stateApprovalAction}">
<property name="createXml">
<true/>
</property>
</event-listener>
Java-fragment:
public void setCreateXml(boolean createXml) {
this.createXml = createXml;
}
Workaround: changing the Java-side to use a Boolean instead of a boolean for the method parameter.
While there is a workaround, I will still suggest supporting both Boolean and boolean-based setters.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2859) spring3 cause autowire exception
by Huisheng Xu (JIRA)
spring3 cause autowire exception
--------------------------------
Key: JBPM-2859
URL: https://jira.jboss.org/jira/browse/JBPM-2859
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: spring 3
Reporter: Huisheng Xu
The spring3 includes some beans with type java.util.Map. When the autowire of ObjectDescriptor is true, The ObjectDescriptor will try to find related bean by field type. When a component have fields with type java.util.Map. The ObjectDescriptor will get these beans from spring3 and set them as field value.
For example, RepositoryCacheImpl have two Map fields: deployments and deploymentClassLoaders. And RepositoryCacheBinding use autowire to configure it. So when we use jBPM with spring3. The deployments field in RepositoryCacheImpl will be auto set value like this:
{java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, sun.boot.library.path=D:\apps\jdk1.5.0_15\jre\bin,
java.vm.version=1.5.0_15-b04, java.vm.vendor=Sun Microsystems Inc., java.vendor.url=http://java.sun.com/, path.separator
=;, java.vm.name=Java HotSpot(TM) Client VM, file.encoding.pkg=sun.io, sun.java.launcher=SUN_STANDARD, user.country=CN,
sun.os.patch.level=Service Pack 3, java.vm.specification.name=Java Virtual Machine Specification, user.dir=D:\svn\jbpm4s
ample, java.runtime.version=1.5.0_15-b04, basedir=D:\svn\jbpm4sample, java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironm
ent, java.endorsed.dirs=D:\apps\jdk1.5.0_15\jre\lib\endorsed, os.arch=x86, surefire.real.class.path=C:\DOCUME~1\ADMINI~1
\LOCALS~1\Temp\surefirebooter30085.jar, java.io.tmpdir=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\, line.separator=
, java.vm.specification.vendor=Sun Microsystems Inc., user.variant=, os.name=Windows XP, sun.jnu.encoding=GBK, java.libr
ary.path=D:\apps\jdk1.5.0_15\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;d:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.
1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\Thunder Network\KanKan\Cod
ecs;C:\Program Files\Subversion\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\TortoiseGit\bin;C:\Program Files\M
icrosoft SQL Server\90\Tools\binn\;D:\apps\jdk1.5.0_15\bin;D:\apps\apache-ant-1.7.1\bin;D:\apps\apache-maven-2.2.1\bin;d
:\Program Files\Google\google_appengine;C:\Program Files\StormII\Codec;C:\Program Files\StormII;D:\apps\AdobeAIRSDK\bin;
D:\apps\flex_sdk_3\bin;;, surefire.test.class.path=D:\svn\jbpm4sample\target\test-classes;D:\svn\jbpm4sample\target\clas
ses;D:\.m2\repository\org\jbpm\jbpm4\jbpm-jpdl\4.3\jbpm-jpdl-4.3.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-pvm\4.3\jbpm-
pvm-4.3.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-api\4.3\jbpm-api-4.3.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-log\4.3
\jbpm-log-4.3.jar;D:\.m2\repository\log4j\log4j\1.2.14\log4j-1.2.14.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-test-base\
4.3\jbpm-test-base-4.3.jar;D:\.m2\repository\junit\junit\4.8.1\junit-4.8.1.jar;D:\.m2\repository\org\hibernate\hibernate
-core\3.3.1.GA\hibernate-core-3.3.1.GA.jar;D:\.m2\repository\antlr\antlr\2.7.6\antlr-2.7.6.jar;D:\.m2\repository\commons
-collections\commons-collections\3.1\commons-collections-3.1.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\
.m2\repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;D:\.m2\repository\javax\transaction\jta\1.1\jta-1.1.jar;D:\.
m2\repository\org\slf4j\slf4j-api\1.5.2\slf4j-api-1.5.2.jar;D:\.m2\repository\org\slf4j\slf4j-jdk14\1.5.2\slf4j-jdk14-1.
5.2.jar;D:\.m2\repository\com\mockrunner\mockrunner\0.4.1\mockrunner-0.4.1.jar;D:\.m2\repository\org\mockejb\mockejb\0.6
-beta2\mockejb-0.6-beta2.jar;D:\.m2\repository\cglib\cglib-nodep\2.1_3\cglib-nodep-2.1_3.jar;D:\.m2\repository\juel\juel
\2.1.0\juel-2.1.0.jar;D:\.m2\repository\juel\juel-impl\2.1.0\juel-impl-2.1.0.jar;D:\.m2\repository\juel\juel-engine\2.1.
0\juel-engine-2.1.0.jar;D:\.m2\repository\org\beanshell\bsh\2.0b5\bsh-2.0b5.jar;D:\.m2\repository\org\hibernate\hibernat
e-entitymanager\3.4.0.GA\hibernate-entitymanager-3.4.0.GA.jar;D:\.m2\repository\org\hibernate\ejb3-persistence\1.0.2.GA\
ejb3-persistence-1.0.2.GA.jar;D:\.m2\repository\org\hibernate\hibernate-commons-annotations\3.1.0.GA\hibernate-commons-a
nnotations-3.1.0.GA.jar;D:\.m2\repository\org\hibernate\hibernate-annotations\3.4.0.GA\hibernate-annotations-3.4.0.GA.ja
r;D:\.m2\repository\javassist\javassist\3.4.GA\javassist-3.4.GA.jar;D:\.m2\repository\org\livetribe\livetribe-jsr223\2.0
.5\livetribe-jsr223-2.0.5.jar;D:\.m2\repository\javax\mail\mail\1.4.1\mail-1.4.1.jar;D:\.m2\repository\javax\activation\
activation\1.1\activation-1.1.jar;D:\.m2\repository\org\hsqldb\hsqldb\1.8.0.10\hsqldb-1.8.0.10.jar;D:\.m2\repository\org
\springframework\spring-orm\3.0.2.RELEASE\spring-orm-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-bean
s\3.0.2.RELEASE\spring-beans-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-core\3.0.2.RELEASE\spring-co
re-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-asm\3.0.2.RELEASE\spring-asm-3.0.2.RELEASE.jar;D:\.m2\
repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-
jdbc\3.0.2.RELEASE\spring-jdbc-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\3.0.2.RELEASE\spring-tx
-3.0.2.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframewo
rk\spring-aop\3.0.2.RELEASE\spring-aop-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\3.0.2.RELE
ASE\spring-context-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\3.0.2.RELEASE\spring-expres
sion-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-test\3.0.2.RELEASE\spring-test-3.0.2.RELEASE.jar;, j
ava.specification.name=Java Platform API Specification, java.class.version=49.0, sun.management.compiler=HotSpot Client
Compiler, os.version=5.1, user.home=C:\Documents and Settings\Administrator, user.timezone=Asia/Shanghai, java.awt.print
erjob=sun.awt.windows.WPrinterJob, file.encoding=GBK, java.specification.version=1.5, java.class.path=D:\svn\jbpm4sample
\target\test-classes;D:\svn\jbpm4sample\target\classes;D:\.m2\repository\org\jbpm\jbpm4\jbpm-jpdl\4.3\jbpm-jpdl-4.3.jar;
D:\.m2\repository\org\jbpm\jbpm4\jbpm-pvm\4.3\jbpm-pvm-4.3.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-api\4.3\jbpm-api-4.
3.jar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-log\4.3\jbpm-log-4.3.jar;D:\.m2\repository\log4j\log4j\1.2.14\log4j-1.2.14.j
ar;D:\.m2\repository\org\jbpm\jbpm4\jbpm-test-base\4.3\jbpm-test-base-4.3.jar;D:\.m2\repository\junit\junit\4.8.1\junit-
4.8.1.jar;D:\.m2\repository\org\hibernate\hibernate-core\3.3.1.GA\hibernate-core-3.3.1.GA.jar;D:\.m2\repository\antlr\an
tlr\2.7.6\antlr-2.7.6.jar;D:\.m2\repository\commons-collections\commons-collections\3.1\commons-collections-3.1.jar;D:\.
m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;D:\.m2\re
pository\javax\transaction\jta\1.1\jta-1.1.jar;D:\.m2\repository\org\slf4j\slf4j-api\1.5.2\slf4j-api-1.5.2.jar;D:\.m2\re
pository\org\slf4j\slf4j-jdk14\1.5.2\slf4j-jdk14-1.5.2.jar;D:\.m2\repository\com\mockrunner\mockrunner\0.4.1\mockrunner-
0.4.1.jar;D:\.m2\repository\org\mockejb\mockejb\0.6-beta2\mockejb-0.6-beta2.jar;D:\.m2\repository\cglib\cglib-nodep\2.1_
3\cglib-nodep-2.1_3.jar;D:\.m2\repository\juel\juel\2.1.0\juel-2.1.0.jar;D:\.m2\repository\juel\juel-impl\2.1.0\juel-imp
l-2.1.0.jar;D:\.m2\repository\juel\juel-engine\2.1.0\juel-engine-2.1.0.jar;D:\.m2\repository\org\beanshell\bsh\2.0b5\bsh
-2.0b5.jar;D:\.m2\repository\org\hibernate\hibernate-entitymanager\3.4.0.GA\hibernate-entitymanager-3.4.0.GA.jar;D:\.m2\
repository\org\hibernate\ejb3-persistence\1.0.2.GA\ejb3-persistence-1.0.2.GA.jar;D:\.m2\repository\org\hibernate\hiberna
te-commons-annotations\3.1.0.GA\hibernate-commons-annotations-3.1.0.GA.jar;D:\.m2\repository\org\hibernate\hibernate-ann
otations\3.4.0.GA\hibernate-annotations-3.4.0.GA.jar;D:\.m2\repository\javassist\javassist\3.4.GA\javassist-3.4.GA.jar;D
:\.m2\repository\org\livetribe\livetribe-jsr223\2.0.5\livetribe-jsr223-2.0.5.jar;D:\.m2\repository\javax\mail\mail\1.4.1
\mail-1.4.1.jar;D:\.m2\repository\javax\activation\activation\1.1\activation-1.1.jar;D:\.m2\repository\org\hsqldb\hsqldb
\1.8.0.10\hsqldb-1.8.0.10.jar;D:\.m2\repository\org\springframework\spring-orm\3.0.2.RELEASE\spring-orm-3.0.2.RELEASE.ja
r;D:\.m2\repository\org\springframework\spring-beans\3.0.2.RELEASE\spring-beans-3.0.2.RELEASE.jar;D:\.m2\repository\org\
springframework\spring-core\3.0.2.RELEASE\spring-core-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-asm
\3.0.2.RELEASE\spring-asm-3.0.2.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.
1.jar;D:\.m2\repository\org\springframework\spring-jdbc\3.0.2.RELEASE\spring-jdbc-3.0.2.RELEASE.jar;D:\.m2\repository\or
g\springframework\spring-tx\3.0.2.RELEASE\spring-tx-3.0.2.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopa
lliance-1.0.jar;D:\.m2\repository\org\springframework\spring-aop\3.0.2.RELEASE\spring-aop-3.0.2.RELEASE.jar;D:\.m2\repos
itory\org\springframework\spring-context\3.0.2.RELEASE\spring-context-3.0.2.RELEASE.jar;D:\.m2\repository\org\springfram
ework\spring-expression\3.0.2.RELEASE\spring-expression-3.0.2.RELEASE.jar;D:\.m2\repository\org\springframework\spring-t
est\3.0.2.RELEASE\spring-test-3.0.2.RELEASE.jar;, user.name=Administrator, java.vm.specification.version=1.0, java.home=
D:\apps\jdk1.5.0_15\jre, sun.arch.data.model=32, user.language=zh, java.specification.vendor=Sun Microsystems Inc., awt.
toolkit=sun.awt.windows.WToolkit, java.vm.info=mixed mode, sharing, java.version=1.5.0_15, java.ext.dirs=D:\apps\jdk1.5.
0_15\jre\lib\ext, sun.boot.class.path=D:\apps\jdk1.5.0_15\jre\lib\rt.jar;D:\apps\jdk1.5.0_15\jre\lib\i18n.jar;D:\apps\jd
k1.5.0_15\jre\lib\sunrsasign.jar;D:\apps\jdk1.5.0_15\jre\lib\jsse.jar;D:\apps\jdk1.5.0_15\jre\lib\jce.jar;D:\apps\jdk1.5
.0_15\jre\lib\charsets.jar;D:\apps\jdk1.5.0_15\jre\classes, java.vendor=Sun Microsystems Inc., localRepository=D:/.m2/re
pository, file.separator=\, java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi, sun.io.unicode.encoding=Unico
deLittle, sun.cpu.endian=little, sun.desktop=windows, org.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk
14Logger, sun.cpu.isalist=pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86}
And it will cause java.lang.NumberFormatException: For input string: "sun.io.unicode.encoding".
We could change ObjectDescriptor to ignore autowire java.util.Map. Or we could change the SpringContext, when jBPM4 want to get java.util.Map, it should return null.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2478) jBPM4/Spring: unintended wiring PropertiesFactoryBean to RepositoryCacheImpl.deployments field
by Michael Feichtegger (JIRA)
jBPM4/Spring: unintended wiring PropertiesFactoryBean to RepositoryCacheImpl.deployments field
----------------------------------------------------------------------------------------------
Key: JBPM-2478
URL: https://jira.jboss.org/jira/browse/JBPM-2478
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0
Environment: Windows XP Service Pack 3, JDK 1.6.0_13, Eclipse Galileo JavaEE, jBPM4
Reporter: Michael Feichtegger
If you define a spring bean (<bean name="configProperties" class="org.springframework.beans.factory.config.PropertiesFactoryBean" ) this bean will be an instance of java.util.Hashtable (java.util.Properties) at runtime.
During jBPM initialization various ObjectDescriptiors create instances they describe. So do the descriptor of org.jbpm.pvm.internal.repository.RepositoryCacheImpl.
After creation the auto-wire mechanism tries to set-up the fields. In case of RepositoryCacheImpl there is just one field: Map<String, Object> deployments.
The "configProperties" bean will be found in the SpringContext since java.util.Hashtable implements java.util.Map and the field "RepositoryCacheImpl.deployments" will be set because there is just one object of the requested type (java.util.Map). The isAutoWireEnabled attribute is set to "true" (hardcoded) at RepositoryCacheBinding.
This behavior causes a NullPointerException when deleting a deployment
RepositoryCacheImpl.java line 45
deployments.put(deploymentId, null);
That statement works on java.util.HashMap (created when instantiate RepositoryCacheImpl) but not on java.util.Hashtable.
That behaviour might influence several other components.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2760) Fix generics specification in ExecutionService interface
by M M (JIRA)
Fix generics specification in ExecutionService interface
--------------------------------------------------------
Key: JBPM-2760
URL: https://jira.jboss.org/jira/browse/JBPM-2760
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1, jBPM 4.2, jBPM 4.3
Reporter: M M
Currently, some of the ExecutionService interface methods have parameters whose type is specified like
Map<String, Object> variables
However, when attempting to call these with methods with, say, an object of type Map<String,String>, the java compiler will not accept the object without some casting. To fix this, please change the interface to use the wildcard feature of Java 5 generics. This has already been done on other methods. The above would change to:
Map<String, ?> variables
Please also fix the same issue on TaskService (methods setVariables and completeTask). This change would be backwardly-compatible.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2677) Migration of process instances fails when there are no process instances
by Edgar Vonk (JIRA)
Migration of process instances fails when there are no process instances
------------------------------------------------------------------------
Key: JBPM-2677
URL: https://jira.jboss.org/jira/browse/JBPM-2677
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.2
Reporter: Edgar Vonk
When the process definition includes a 'migrate-instances' entry like:
{code}
<migrate-instances versions="*"/>
{code}
The migration of process instances fails when there are no process instances in the jBPM database:
{quote}
EXCEPTION ###########################################
16:15:36,793 INF | [DefaultCommandService] exception while executing command org.jbpm.pvm.internal.cmd.DeployCmd@1a550
f9
java.lang.IndexOutOfBoundsException: fromIndex = -1
at java.util.SubList.<init>(AbstractList.java:600)
at java.util.RandomAccessSubList.<init>(AbstractList.java:758)
at java.util.AbstractList.subList(AbstractList.java:468)
at org.jbpm.pvm.internal.migration.InstanceMigrator.getProcessesToMigrate(InstanceMigrator.java:104)
at org.jbpm.pvm.internal.migration.InstanceMigrator.getProcessInstancesToMigrate(InstanceMigrator.java:84)
[..]
{quote}
This issue is caused by the following code in the InstanceMigrator class:
{code}
private static List<ProcessDefinition> getProcessesToMigrate(String processDefinitionName, MigrationDescriptor migrationDescriptor) {
RepositorySession repositorySession = EnvironmentImpl.getFromCurrent(RepositorySession.class);
List<ProcessDefinition> processDefinitions = repositorySession
.createProcessDefinitionQuery()
.processDefinitionName(processDefinitionName)
.orderAsc(ProcessDefinitionQuery.PROPERTY_VERSION)
.list();
int startIndex = calculateStartIndex(processDefinitions.size() - 1, migrationDescriptor);
int endIndex = calculateEndIndex(processDefinitions.size() - 1, migrationDescriptor);
if (startIndex > endIndex) startIndex = endIndex;
return processDefinitions.subList(startIndex, endIndex);
}
{code}
No check is done to see if the list of processes (processDefinitions) is not empty.
This issue causes our unit tests to fail since our unit tests start with an empty jBPM database.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2838) Mark jboss-j2ee dependency as scope=provided
by M M (JIRA)
Mark jboss-j2ee dependency as scope=provided
--------------------------------------------
Key: JBPM-2838
URL: https://jira.jboss.org/jira/browse/JBPM-2838
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: M M
Please mark the dependency on jboss as <scope>provided</scope>
Here is the relevent section of the jbpm-api pom:
<dependencies>
<dependency>
<groupId>jboss</groupId>
<artifactId>jboss-j2ee</artifactId>
</dependency>
</dependencies>
This is not an issue of determining minimal dependency (it certainly needs this dependency), but rather, decoupling the jbpm api from any specific J2EE vendor implementation or version. Users of the jbpm api will then not have a transitive dependency on a specific version of jboss.
The current workaround is to exclude this dependency when depending on the jbpm api.
--
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, 1 month
[JBoss JIRA] Created: (JBPM-2537) A triggered timer does not end the task which is left
by Alexis Seigneurin (JIRA)
A triggered timer does not end the task which is left
-----------------------------------------------------
Key: JBPM-2537
URL: https://jira.jboss.org/jira/browse/JBPM-2537
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.0, jBPM 4.1
Reporter: Alexis Seigneurin
In my process definition, "task1" has a transition with a due date. When this timer is triggered by the job executor, the transition takes the process to "task2" but "task1" still looks active. For instance, when I run a "task query", instead of only finding "task2", both "task1" and "task2" are found.
Here is my process definition:
<?xml version="1.0" encoding="UTF-8"?>
<process name="test1" xmlns="http://jbpm.org/4.0/jpdl">
<start g="-9,192,48,48" name="start1">
<transition g="-44,-18" name="to task3" to="task3" />
</start>
<end g="490,192,48,48" name="end1" />
<task g="272,189,92,52" name="task1">
<transition g="-42,-18" name="to end1" to="end1" />
<transition g="-45,-18" name="to java1" to="reminder">
<timer duedate="10 seconds" />
</transition>
</task>
<java class="fr.idm.SimpleReminder" g="272,316,92,52" method="remind" name="reminder">
<transition to="task2" />
</java>
<end g="626,319,48,48" name="end2" />
<task g="454,316,92,52" name="task2">
<transition g="-42,-18" name="to end2" to="end2" />
</task>
<task g="113,189,92,52" name="task3">
<transition g="-44,-18" to="task1" name="to end1" />
</task>
</process>
For testing purpose, I introduced "task3" before "task1". It is not listed by the task query, which makes me think that, once "task1" is left, it should no longer be active.
This looks like https://jira.jboss.org/jira/browse/JBPM-967 but the suggested solution does not seem applicable to JBPM 4.x.
I will attached the whole source 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, 1 month