February 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1993) Interface with the JBoss identity component

by Heiko Braun (JIRA)

Interface with the JBoss identity component ------------------------------------------- Key: JBPM-1993 URL: https://jira.jboss.org/jira/browse/JBPM-1993 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Tom Baeyens JBoss Identity IDM 1.0.0-Alpha1: SVN: http://anonsvn.jboss.org/repos/jbossidentity/idm/tags/1.0.0-Alpha1/ Docs: http://www.jboss.org/community/docs/DOC-13258 Quick Start Guide: http://www.jboss.org/community/docs/DOC-13263 -- 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

15 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2002) ElementType is updated every time flush is called by hibernate

by Meghana Joglekar (JIRA)

ElementType is updated every time flush is called by hibernate -------------------------------------------------------------- Key: JBPM-2002 URL: https://jira.jboss.org/jira/browse/JBPM-2002 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: BPEL Affects Versions: jBPM 3.2.0 Reporter: Meghana Joglekar -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1984) Transient variables are not assigned to Sub Process

by Atanas Krachev (JIRA)

Transient variables are not assigned to Sub Process ---------------------------------------------------- Key: JBPM-1984 URL: https://jira.jboss.org/jira/browse/JBPM-1984 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA, jBPM 3.3.0 GA, jBPM 3.2.5 GA , jBPM 3.2.4 GA, jBPM 3.2.3, jBPM 3.2.2 Environment: JVM Reporter: Atanas Krachev Transient variables are not assigned to Sub Process I have a Super Process consisting of few Sub processes and transient variables map is supposed to be assigned to the Sub Processes too in order to be available to them too. But this behavior is true only if we have define at least one Super process variable to be Read by a Sub process. The bug could be resolved if in org.jbpm.graph.node.ProcessState.execute(...) ---------- if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { ContextInstance superContextInstance = executionContext.getContextInstance(); ContextInstance subContextInstance = subProcessInstance.getContextInstance(); subContextInstance.setTransientVariables(superContextInstance.getTransientVariables()); --------- is changed like: --------- ContextInstance superContextInstance = executionContext.getContextInstance(); ContextInstance subContextInstance = subProcessInstance.getContextInstance(); subContextInstance.setTransientVariables(superContextInstance.getTransientVariables()); if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { -- 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

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2013) possibly a missing example in docs

by Darrin Mison (JIRA)

possibly a missing example in docs ---------------------------------- Key: JBPM-2013 URL: https://jira.jboss.org/jira/browse/JBPM-2013 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: jBPM 3.2.3 Reporter: Darrin Mison This exists in http://docs.jboss.com/jbpm/v3.2/userguide/html_single/#configurationthepe... and was included in the SOA docs Should the code example be moved up before the "IMPORTANT" paragraph and the "Like this:" be removed from that paragraph. Or is there a missing example here? 7.2. Configuring the persistence service 7.2.1. The DbPersistenceServiceFactory The DbPersistenceServiceFactory itself has 3 more configuration properties: isTransactionEnabled, sessionFactoryJndiName and dataSourceJndiName. To specify any of these properties in the jbpm.cfg.xml, you need to specify the service factory as a bean in the factory element like this: IMPORTANT: don't mix the short and long notation for configuring the factories. See also Section 6.1, "Customizing factories". If the factory is just a new instance of a class, you can use the factory attribute to refer to the factory class name. But if properties in a factory must be configured, the long notation must be used and factory and bean must be combined as nested elements. Like this: <jbpm-context> <service name="persistence"> <factory> <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isTransactionEnabled"><false /></field> <field name="sessionFactoryJndiName"> <string value="java:/myHibSessFactJndiName" /> </field> <field name="dataSourceJndiName"> <string value="java:/myDataSourceJndiName" /> </field> </bean> </factory> </service> ... </jbpm-context> -- 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

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPM-1441) JBPM.3 failures with sybase 12.5

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1441?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1441: --------------------------------- Fix Version/s: (was: jBPM 3.2.x) > JBPM.3 failures with sybase 12.5 > -------------------------------- > > Key: JBPM-1441 > URL: https://jira.jboss.org/jira/browse/JBPM-1441 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Aleksandar Kostadinov > Assignee: Thomas Diesler > Fix For: SOA 4.2 CP03 > > > Tests failing with sybase 12.5 > JBPM-1177 -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1156) jBPM example: customTaskInstance fails with classcast exception

by Len DiMaggio (JIRA)

jBPM example: customTaskInstance fails with classcast exception ---------------------------------------------------------------- Key: JBPM-1156 URL: http://jira.jboss.com/jira/browse/JBPM-1156 Project: JBoss jBPM Issue Type: Bug Reporter: Len DiMaggio Assigned To: Tom Baeyens Priority: Minor jBPM example: customTaskInstance fails with this exception: See: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088401#4088401 java.lang.ClassCastException: org.jbpm.taskmgmt.exe.TaskInstance at org.jbpm.taskinstance.CustomTaskControllerHandler.initializeTaskVariables(CustomTaskControllerHandler.java:66) at org.jbpm.taskmgmt.def.TaskController.initializeVariables(TaskController.java:82) 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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.taskmgmt.def.TaskController$$EnhancerByCGLIB$$1af08496.initializeVariables(<generated>) at org.jbpm.taskmgmt.exe.TaskInstance.initializeVariables(TaskInstance.java:145) at org.jbpm.taskmgmt.exe.TaskMgmtInstance.createTaskInstance(TaskMgmtInstance.java:136) at org.jbpm.graph.node.TaskNode.execute(TaskNode.java:168) at org.jbpm.graph.def.Node.enter(Node.java:319) 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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$55e0744d.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:394) at org.jbpm.graph.node.StartState.leave(StartState.java:70) 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.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$55e0744d.leave(<generated>) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) at org.jbpm.taskinstance.CustomTaskInstanceTest.createNewProcessInstance(CustomTaskInstanceTest.java:162) at org.jbpm.taskinstance.CustomTaskInstanceTest.testCustomTaskInstance(CustomTaskInstanceTest.java:125) 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 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 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) <classpathentry kind="lib" path="/opt/GA/jboss-soa-p-standalone.4.2.0/jbpm-jpdl/jbpm-jpdl.jar"/> <classpathentry kind="lib" path="/opt/GA/jboss-soa-p.4.2.0/seam/lib/jbpm-3.1.4.jar"/> <classpathentry kind="lib" path="/opt/GA/jboss-soa-p-standalone.4.2.0/jbpm-jpdl/lib/hibernate3.jar"/> <classpathentry kind="lib" path="/opt/GA/jboss-soa-p-standalone.4.2.0/jbpm-jpdl/lib/dom4j.jar"/> <classpathentry kind="lib" path="/opt/GA/jboss-soa-p-standalone.4.2.0/jbpm-jpdl/jbpm-identity.jar"/> -- 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

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Updated: (JBPM-1443) Follup to SOA-344 - should the namespace reference be removed?

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1443?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1443: --------------------------------- Fix Version/s: (was: jBPM 3.2.x) > Follup to SOA-344 - should the namespace reference be removed? > -------------------------------------------------------------- > > Key: JBPM-1443 > URL: https://jira.jboss.org/jira/browse/JBPM-1443 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Environment: standalone-soa-4.2.0.CR1.zip > soa-4.2.0.CR1.zip > Reporter: Len DiMaggio > Assignee: Thomas Diesler > Fix For: SOA 4.2 CP03 > > > Followup to SOA-344 > The fix in SOA-344 was to remove the namespace reference. Don't we need this? -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1445) The jBPM 'websale' sample application fails

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1445?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1445: --------------------------------- Fix Version/s: (was: jBPM 3.2.x) > The jBPM 'websale' sample application fails > -------------------------------------------- > > Key: JBPM-1445 > URL: https://jira.jboss.org/jira/browse/JBPM-1445 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Environment: JBoss Developer Studio > Build id: 1.0.0.GA > SOA-P GA > /opt/GA/soa-4.2.0.GA.zip > /opt/GA/standalone-soa-4.2.0.GA.zip > RHEL5 > Linux ldimaggi.csb 2.6.18-53.1.13.el5 #1 SMP Mon Feb 11 13:27:52 EST 2008 i686 i686 i386 GNU/Linux > Sun Java 1.5 > java version "1.5.0_14" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) > Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode) > RDBMS > H2, version: 1.0.66 (2008-01-18) > CPU > cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 13 > model name : Intel(R) Pentium(R) M processor 1.70GHz > stepping : 6 > cpu MHz : 1700.000 > cache size : 2048 KB > fdiv_bug : no > hlt_bug : no > f00f_bug : no > coma_bug : no > fpu : yes > fpu_exception : yes > cpuid level : 2 > wp : yes > flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up est tm2 > bogomips : 3398.35 > Reporter: Len DiMaggio > Fix For: SOA 4.2 CP03 > > Attachments: Screenshot-1.png, server.log, server.log, server.log.gz > > > The jBPM 'websale' sample application fails - when an order is approved (OK is selected). This exception is displayed back to the user: > Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown. > Closing the database context failed: An exception of type org.jbpm.JbpmException was thrown, with the message: problem closing services {persistence=org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifies user managed transactions} > The server.log is attached. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1155) jBPM example "mail" - missing import statements, etc.

by Len DiMaggio (JIRA)

jBPM example "mail" - missing import statements, etc. ----------------------------------------------------- Key: JBPM-1155 URL: http://jira.jboss.com/jira/browse/JBPM-1155 Project: JBoss jBPM Issue Type: Bug Components: Training Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens Project JIRA for SOA Platform JIRA: http://jira.jboss.com/jira/browse/SOA-483 -- 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

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1439) Migrate jBPM SOA branches to SVN

by Thomas Diesler (JIRA)

Migrate jBPM SOA branches to SVN -------------------------------- Key: JBPM-1439 URL: https://jira.jboss.org/jira/browse/JBPM-1439 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: SOA 4.3 -- 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

15 years, 10 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2009