December 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1840) Business process instance data should be deleted automatically

by Thomas Diesler (JIRA)

Business process instance data should be deleted automatically -------------------------------------------------------------- Key: JBPM-1840 URL: https://jira.jboss.org/jira/browse/JBPM-1840 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 4.0.x when the process is finished -- 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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1838) Automatic O/R mapping of non-primitive process variables

by Thomas Diesler (JIRA)

Automatic O/R mapping of non-primitive process variables -------------------------------------------------------- Key: JBPM-1838 URL: https://jira.jboss.org/jira/browse/JBPM-1838 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 4.0.x e.g. Customer, Order -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1318) update the new project infrastructure on the website

by Tom Baeyens (JIRA)

update the new project infrastructure on the website ---------------------------------------------------- Key: JBPM-1318 URL: http://jira.jboss.com/jira/browse/JBPM-1318 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Baeyens Assigned To: Koen Aers -- 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

17 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1246) create descriptions for all targets in build files

by Tom Baeyens (JIRA)

create descriptions for all targets in build files -------------------------------------------------- Key: JBPM-1246 URL: http://jira.jboss.com/jira/browse/JBPM-1246 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Assigned To: Tom Baeyens -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1903) java:/comp/env JNDI Namespace not found within ActionHandler Implementations

by Robert Schmelzer (JIRA)

java:/comp/env JNDI Namespace not found within ActionHandler Implementations ---------------------------------------------------------------------------- Key: JBPM-1903 URL: https://jira.jboss.org/jira/browse/JBPM-1903 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 GA Environment: JBoss 4.2.3 GA with MySQL5 Database jBPM Enterprise Deployment Reporter: Robert Schmelzer When you try to lookup the JNDI Namespace java:comp/env in an enterprise deployment wihtin an ActionHandler implementation it will throw an NameNotFoundException. So it is not possible to lookup ejb or other component local stuff within ActionHandler implementations. In special this also affects you, when you signal a token within an ActionHandler and any of the following Node is async using the JMSMessgeService because the JMS implementation will also make a lookup on the connection factory using the comp/env Namespace. The reason for this is the change in the classloader when executing ActionHandlers. The contex class loader is by default changed to the ProcessClassLoader using the UCL as parent. But JBoss uses the ContextClassLoader ot scope the comp/env Namespace. When using the original context class loader as the parent for the ProcessClassLoader it works again. -- 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

17 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-1782) fix JoinExecutionDbTest on postgresql

by Tom Baeyens (JIRA)

fix JoinExecutionDbTest on postgresql ------------------------------------- Key: JBPM-1782 URL: https://jira.jboss.org/jira/browse/JBPM-1782 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA Failed org.jbpm.jpdl.exe.JoinExecutionDbTest.testJoinPersistence Failing for the past 3 builds (Since Unstable#31 ) Took 0 sec. Error Message Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#3113] Stacktrace org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#3113] at org.hibernate.persister.entity.AbstractEntityPersister.forceVersionIncrement(AbstractEntityPersister.java:1239) at org.hibernate.event.def.AbstractLockUpgradeEventListener.upgradeLock(AbstractLockUpgradeEventListener.java:82) at org.hibernate.event.def.DefaultLockEventListener.onLock(DefaultLockEventListener.java:64) at org.hibernate.impl.SessionImpl.fireLock(SessionImpl.java:584) at org.hibernate.impl.SessionImpl.lock(SessionImpl.java:576) at org.jbpm.graph.node.Join.execute(Join.java:121) at org.jbpm.graph.def.Node.enter(Node.java:314) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:389) at org.jbpm.graph.exe.Token.signal(Token.java:192) at org.jbpm.graph.exe.Token.signal(Token.java:140) at org.jbpm.jpdl.exe.JoinExecutionDbTest.testJoinPersistence(JoinExecutionDbTest.java:57) 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 junit.framework.TestCase.runTest(TestCase.java:154) at org.jbpm.AbstractJbpmTestCase.runTest(AbstractJbpmTestCase.java:57) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- 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

17 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-1753) review event names

by Tom Baeyens (JIRA)

review event names ------------------ Key: JBPM-1753 URL: https://jira.jboss.org/jira/browse/JBPM-1753 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Fix For: PVM 1.0.0 Beta1 process events should be start stop to be in sync with the API start-stop. node-begin and node-end might be changed to activity-start and activity-stop maybe process and activity event names could be unified ? -- 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

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1163) Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter

by Julien Kronegg (JIRA)

Bad property format of hibernate.cfg.xml snippet in the user guide "Persistence" chapter ---------------------------------------------------------------------------------------- Key: JBPM-1163 URL: http://jira.jboss.com/jira/browse/JBPM-1163 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: CVS code JBPM 3.2.2 downloaded on 2008.04.18. Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Optional Fix For: jBPM 3.3 In "/jbpm.3/jpdl/userguide/en/modules/persistence.xml" (CVS version 1.11), the "Managed transactions" section describe the most important configuration property from the "hibernate.cfg.xml" file as follow: "hibernate.connection.datasource= --datasource JNDI name-- like e.g. java:/DefaultDS" This property should be described using a XML format because the "hibernate.cfg.xml" in in XML format, for example: <property name="hibernate.connection.datasource"> --datasource JNDI name-- like e.g. java:/DefaultDS </property> Note: not tested on the german documentation. -- 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

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1161) Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1

by Julien Kronegg (JIRA)

Bad references to property "jbpm.hibernate.cfg.xml" from the "jbpm.properties" file removed in JBPM 3.1 ------------------------------------------------------------------------------------------------------- Key: JBPM-1161 URL: http://jira.jboss.com/jira/browse/JBPM-1161 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: CVS code of JBPM 3.2.2 obtained on 2008.04.18 Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The JBPM 3.2.2 user guide refers to the file "jbpm.properties", which was replaced by "jbpm.cfg.xml" in version JBPM 3.1 (see http://sourceforge.net/project/shownotes.php?release_id=383725&group_id=7... ). While references to "jbpm.properties" may be valid in a change log or a migration guide, they are not valid in the following files. /jbpm.3/jpdl/userguide/en/modules/persistence.xml (CVS version 1.11): In the sentence "Note that the hibernate configuration file resource is mapped in the property 'jbpm.hibernate.cfg.xml' and can be customized in the jbpm.cfg.xml", the "jbpm.hibernate.cfg.xml" property name should be replaced by "resource.hibernate.cfg.xml" (i.e. the property of the file snippet shown just below that sentence). /jbpm.3/jpdl/userguide/en/modules/configuration.xml (CVS version 1.7): The sentence "Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the jbpm.hibernate.cfg.xml property in the jbpm.properties file." should be replaced by: "Location: <literal>hibernate.cfg.xml</literal> unless specified otherwise in the resource.hibernate.cfg.xml property in the jbpm.cfg.xml file." -- 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

17 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1897) Unable to Login in JBPM console

by Santayan Biswas (JIRA)

Unable to Login in JBPM console ------------------------------- Key: JBPM-1897 URL: https://jira.jboss.org/jira/browse/JBPM-1897 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 3.3.0 GA Reporter: Santayan Biswas I am very new in JBPM. By default JBPM uses Hypersonic database. But in my application I need to connect to SQL Server, so I changes the related files accordingly. But I can not find the table name and script from where it picks the login user information. So I am unable to login in JBPM console. Can anyone please help me regarding this. I am using JBOSS 4.2.3 and JBPM 3.3.0...Please help -- 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

17 years, 3 months

5
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2008