June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1956) Integration API impl. breaks reporting

by Heiko Braun (JIRA)

Integration API impl. breaks reporting -------------------------------------- Key: JBPM-1956 URL: https://jira.jboss.org/jira/browse/JBPM-1956 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun The instance start dates are not set. -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2140) the "version" of the processDefinition in db is a Long type not a Sting type

by fang changjiang (JIRA)

the "version" of the processDefinition in db is a Long type not a Sting type -------------------------------------------------------------------------------- Key: JBPM-2140 URL: https://jira.jboss.org/jira/browse/JBPM-2140 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: PVM Affects Versions: jBPM 4.0.0.Beta1 Environment: WINDOWS XP Eclipse JBOSS AS 4.2.2GA jbpm 4.0.0 Trunk Reporter: fang changjiang when I call ExecutionService.startProcessInstanceById() , I meet a Exception " exception while executing command org.jbpm.pvm.internal.cmd.StartProcessInstanceCmd@f9d4f7 java.lang.ClassCastException: java.lang.Long at org.jbpm.jpdl.internal.repository.JpdlDeployer.deploy(JpdlDeployer.java:72) " so I debug this call process, I find the root cause of the exception is in this segment " String version = (String) deployment.getObjectProperty(processDefinitionName, KEY_VERSION); " I find in the "jbpm.repository.hbm.xml" have " <property name="longValue" column="LONGVAL_" /> " map. I find in DeploymentProperty class the longValue is long type . so the Long type can't cast to String -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2276) net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0

by Jeff Yu (JIRA)

net.sf.xframe.xsddoc.ProcessorException in jBPM4 with maven 2.1.0 ----------------------------------------------------------------- Key: JBPM-2276 URL: https://jira.jboss.org/jira/browse/JBPM-2276 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.0.Beta2 Reporter: Jeff Yu By installing the maven 2.1.0, and then run: mvn clean install -Pschemadoc, you will have following exceptions: (With maven 2.0.9, I don't see this error) Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more Caused by: java.io.FileNotFoundException: /local/works/jbpm4-idm/modules/api/local/works/jbpm4-idm/modules/api/src/main/resources/jpdl-4.0.xsd (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at java.io.FileInputStream.<init>(FileInputStream.java:66) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:184) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:798) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146) at net.sf.xframe.xsddoc.Processor.getDocument(Processor.java:1253) at net.sf.xframe.xsddoc.Processor.processImport(Processor.java:990) at net.sf.xframe.xsddoc.Processor.processComponent(Processor.java:779) at net.sf.xframe.xsddoc.Processor.processComponents(Processor.java:747) at net.sf.xframe.xsddoc.Processor.process(Processor.java:719) at net.sf.xframe.xsddoc.Processor.process(Processor.java:691) at net.sf.xframe.xsddoc.Processor.execute(Processor.java:525) ... 25 more -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1365) Add QA for mssql

by Thomas Diesler (JIRA)

Add QA for mssql ---------------- Key: JBPM-1365 URL: http://jira.jboss.com/jira/browse/JBPM-1365 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2316) review executability of examples in console

by Tom Baeyens (JIRA)

review executability of examples in console ------------------------------------------- Key: JBPM-2316 URL: https://jira.jboss.org/jira/browse/JBPM-2316 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.0 Joram, can you see if all examples are executable in the console ? -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2115) jBPM testsuite hangs when executed with DB2

by Jiri Pechanec (JIRA)

jBPM testsuite hangs when executed with DB2 ------------------------------------------- Key: JBPM-2115 URL: https://jira.jboss.org/jira/browse/JBPM-2115 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM-3.2.5.SP3 Environment: DB2 9.1, JDBC driver 3.1.57, RHEL4 Reporter: Jiri Pechanec The jBPM test suite completely hangs when the following test cases are executed org/jbpm/perf/SimplePerformanceTest.java org/jbpm/job/executor/JobExecutorDbTest.java org/jbpm/jbpm983/JBPM983Test.java -- 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, 10 months

4
18
0 / 0

[JBoss JIRA] Created: (JBPM-2353) remove explicit jta transaction demarcation in console and deployer

by Tom Baeyens (JIRA)

remove explicit jta transaction demarcation in console and deployer ------------------------------------------------------------------- Key: JBPM-2353 URL: https://jira.jboss.org/jira/browse/JBPM-2353 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.1 transactions should only be handled by the command service transaction interceptors. this is necessary to make jbpm available on any environment (tomcat, other app servers). -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1995) Provide a documented dev process that copes with database changes across releases

by Heiko Braun (JIRA)

Provide a documented dev process that copes with database changes across releases --------------------------------------------------------------------------------- Key: JBPM-1995 URL: https://jira.jboss.org/jira/browse/JBPM-1995 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assignee: Heiko Braun Fix For: jBPM 4.0.0 Alpha2 Make DB changes visible and provide a QA process to it. -- 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, 10 months

3
13
0 / 0

[JBoss JIRA] Created: (JBPM-2335) Subprocess Element causes Exception if followed by an <end> Element

by Flavio DonzÃ© (JIRA)

Subprocess Element causes Exception if followed by an <end> Element ------------------------------------------------------------------- Key: JBPM-2335 URL: https://jira.jboss.org/jira/browse/JBPM-2335 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.CR1 Reporter: Flavio DonzÃ© See the forum reference for the description. See the attached TestCase.zip to reproduce the behavior. -- 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, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (JBPM-2194) cant share jars

by David Schlotfeldt (JIRA)

cant share jars --------------- Key: JBPM-2194 URL: https://jira.jboss.org/jira/browse/JBPM-2194 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.6.SP1 Reporter: David Schlotfeldt Priority: Critical You can't share the jbpm jars. Each application must have its own copy since classes like http://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.6.SP1/modules/cor... use static variables. This is a LARGE issue. JBoss Seam for example set settings on UserCodeInterceptorConfig and JbpmExpressionEvaluator. These settings will mess will affect ALL applications that share the same class definitions since the settings are a on static variable. -- 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, 11 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009