May 2009 - jbpm-issues - Jboss List Archives

[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

15 years, 3 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

15 years, 4 months

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

15 years, 4 months

4
18
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

15 years, 4 months

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

15 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2092) Byte Array Should Be In Default Cache Configuration

by Brad Davis (JIRA)

Byte Array Should Be In Default Cache Configuration --------------------------------------------------- Key: JBPM-2092 URL: https://jira.jboss.org/jira/browse/JBPM-2092 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine, Documentation Affects Versions: jBPM 3.3.1 GA Reporter: Brad Davis The hibernate configuration should cache byte array by default. It is missing from the caching configuration. This leads to major performance issues when deploying handler logic classes [java action handlers and decision handlers for example] to the 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2093) Stabilize EjbSchedulerTest.testScheduleFork under MySQL

by Alejandro Guizar (JIRA)

Stabilize EjbSchedulerTest.testScheduleFork under MySQL ------------------------------------------------------- Key: JBPM-2093 URL: https://jira.jboss.org/jira/browse/JBPM-2093 Project: JBoss jBPM Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.6 GA , jBPM-3.2.5.SP3 Environment: JBoss 5.0.0.GA MySQL 5.0.67 Sun JDK 1.5.0.16 Reporter: Alejandro Guizar testScheduleFork fails with: org.jbpm.JbpmException: event 'process-end' did not occur within 300000 ms at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:125) at org.jbpm.graph.def.EventCallback.waitForEvent(EventCallback.java:106) at org.jbpm.enterprise.ejbtimer.EjbSchedulerTest.testScheduleFork(EjbSchedulerTest.java:265) -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1367) Add QA for oracle

by Thomas Diesler (JIRA)

Add QA for oracle ----------------- Key: JBPM-1367 URL: http://jira.jboss.com/jira/browse/JBPM-1367 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

15 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBPM-1286) Provide minimal console test coverage

by Thomas Diesler (JIRA)

Provide minimal console test coverage ------------------------------------- Key: JBPM-1286 URL: http://jira.jboss.com/jira/browse/JBPM-1286 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2119) Work around the need for an extra column to persist field Join.parentLockMode

by Alejandro Guizar (JIRA)

Work around the need for an extra column to persist field Join.parentLockMode ----------------------------------------------------------------------------- Key: JBPM-2119 URL: https://jira.jboss.org/jira/browse/JBPM-2119 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM-3.2.5.SP4 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Blocker Fix For: jBPM 3.2.7 GA In JBPM-1755, a new column PARENTLOCKMODE_ was added to table JBPM_NODE for persisting field Join.parentLockMode. Turns out the schema change is a barrier for our customers to upgrade to newer versions. The proposed solution is to provide two different mappings for the Join class, with and without the column. The provided Hibernate configuration will include the mapping without the column by default. Interested parties may inclde the version with the column in their own Hibernate configuration. -- 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, 5 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues May 2009