April 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1160) Bad link to documentation in org.jbpm.context.exe.ContextInstance javadoc

by Julien Kronegg (JIRA)

Bad link to documentation in org.jbpm.context.exe.ContextInstance javadoc ------------------------------------------------------------------------- Key: JBPM-1160 URL: http://jira.jboss.com/jira/browse/JBPM-1160 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: ContextInstance.java (CVS version 1.2) Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The class javadoc states: "More information on context and process variableInstances can be found in <a href="../../../../../userguide/en/html/reference.html#context">the userguide, section context</a>" This link does not exist in version 3.2.2 and should be corrected. The good link is ".../userguide/html/context.html" (chapter title is "10. Context"). -- 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

16 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1132) bad variable "instanceId" in CancelProcessInstanceCommand with query GraphSession.findSubProcessInstances

by jerome tellier (JIRA)

bad variable "instanceId" in CancelProcessInstanceCommand with query GraphSession.findSubProcessInstances ---------------------------------------------------------------------------------------------------------- Key: JBPM-1132 URL: http://jira.jboss.com/jira/browse/JBPM-1132 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: jerome tellier Assigned To: Tom Baeyens Priority: Minor the method CancelProcessInstanceCommand.cancelSubProcesses use "instanceId" in the query findSubProcessInstances, but it was renamed "processInstance" in the hql query in 3.2.2. -- 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

16 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1141) The jBPM 'websale' sample application fails - project JIRA for SOA-446

by Len DiMaggio (JIRA)

The jBPM 'websale' sample application fails - project JIRA for SOA-446 ---------------------------------------------------------------------- Key: JBPM-1141 URL: http://jira.jboss.com/jira/browse/JBPM-1141 Project: JBoss jBPM Issue Type: Bug Components: Training Affects Versions: jBPM jPDL 3.2.2 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 Assigned To: Tom Baeyens Details are in: http://jira.jboss.com/jira/browse/SOA-446 -- 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

16 years, 8 months

3
5
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

16 years, 8 months

3
5
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

16 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1157) Broken links in jBPM examples/readme.html

by Len DiMaggio (JIRA)

Broken links in jBPM examples/readme.html ----------------------------------------- Key: JBPM-1157 URL: http://jira.jboss.com/jira/browse/JBPM-1157 Project: JBoss jBPM Issue Type: Bug Components: Documentation 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-485 -- 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

16 years, 8 months

3
6
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

16 years, 9 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

16 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1138) deleting a processInstance without any log related cause an Exception

by Dino Lupo (JIRA)

deleting a processInstance without any log related cause an Exception --------------------------------------------------------------------- Key: JBPM-1138 URL: http://jira.jboss.com/jira/browse/JBPM-1138 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: Windows, Linux, JBoss AS 4.2.2 GA Reporter: Dino Lupo Assigned To: Tom Baeyens When deleting process instances calling graphSession.deleteProcessInstance(processInstance); if a process instance doesn't have any logs, an hibernate error occurs. -- 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

16 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1153) JbpmVariableResolver

by mohankishore (JIRA)

JbpmVariableResolver -------------------- Key: JBPM-1153 URL: http://jira.jboss.com/jira/browse/JBPM-1153 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: mohankishore Assigned To: Tom Baeyens http://fisheye.jboss.org/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/org/jb... line 48 Should be looking for the presence of the variable against the current token (not the root token): It should be: && (contextInstance.hasVariable(name, token)) and not just: && (contextInstance.hasVariable(name)) -- 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

16 years, 9 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues April 2008