[JBoss JIRA] Created: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)
3:47 p.m.
Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked
in 3.2.2)
--------------------------------------------------------------------------------------------
Key: JBPM-1376
URL: http://jira.jboss.com/jira/browse/JBPM-1376
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jPDL 3
Affects Versions: jPDL 3.2.3
Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13
Reporter: Joram Barrez
Priority: Critical
Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which
is not named 'jbpm.cfg.xml'.
See forum reference for more information and test class. Test class works for JPDL 3.2.2,
but not for 3.2.3.
Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should
not fail to start and use the standard config which is in the distribution.
--
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
3:49 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)
[ http://jira.jboss.com/jira/browse/JBPM-1376?page=all ]
Joram Barrez updated JBPM-1376:
-------------------------------
Attachment: ScriptExpressionTest.java
Test class. With JPDL 3.2.3 produces following stack trace:
org.jbpm.JbpmException: couldn't parse jbpm configuration from resource
'jbpm.cfg.xml'
at org.jbpm.JbpmConfiguration.getInstance(JbpmConfiguration.java:292)
at org.jbpm.JbpmConfiguration.getInstance(JbpmConfiguration.java:257)
at org.jbpm.JbpmConfiguration$Configs.getObjectFactory(JbpmConfiguration.java:425)
at org.jbpm.JbpmConfiguration$Configs.getObject(JbpmConfiguration.java:437)
at org.jbpm.JbpmConfiguration$Configs.getString(JbpmConfiguration.java:441)
at
org.jbpm.graph.def.ProcessDefinition.createNewProcessDefinition(ProcessDefinition.java:97)
at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:138)
at org.jbpm.graph.def.ProcessDefinition.parseXmlString(ProcessDefinition.java:150)
at ScriptExpressionTest.testExpression(ScriptExpressionTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
Caused by: org.jbpm.JbpmException: jbpm configuration resource 'jbpm.cfg.xml' is
not available
at org.jbpm.JbpmConfiguration.getInstance(JbpmConfiguration.java:286)
... 26 more
Bug in JPDL 3.2.3 when using a configuration file not named
'jbpm.cfg.xml' (worked in 3.2.2)
--------------------------------------------------------------------------------------------
Key: JBPM-1376
URL: http://jira.jboss.com/jira/browse/JBPM-1376
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jPDL 3
Affects Versions: jPDL 3.2.3
Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13
Reporter: Joram Barrez
Priority: Critical
Attachments: ScriptExpressionTest.java
Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which
is not named 'jbpm.cfg.xml'.
See forum reference for more information and test class. Test class works for JPDL 3.2.2,
but not for 3.2.3.
Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should
not fail to start and use the standard config which is in the distribution.
--
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
3:52 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)
[ http://jira.jboss.com/jira/browse/JBPM-1376?page=all ]
Joram Barrez updated JBPM-1376:
-------------------------------
Priority: Major (was: Critical)
Bug in JPDL 3.2.3 when using a configuration file not named
'jbpm.cfg.xml' (worked in 3.2.2)
--------------------------------------------------------------------------------------------
Key: JBPM-1376
URL: http://jira.jboss.com/jira/browse/JBPM-1376
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jPDL 3
Affects Versions: jPDL 3.2.3
Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13
Reporter: Joram Barrez
Attachments: ScriptExpressionTest.java
Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which
is not named 'jbpm.cfg.xml'.
See forum reference for more information and test class. Test class works for JPDL 3.2.2,
but not for 3.2.3.
Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should
not fail to start and use the standard config which is in the distribution.
--
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
10:32 p.m.
New subject: [JBoss JIRA] Resolved: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)
[ http://jira.jboss.com/jira/browse/JBPM-1376?page=all ]
Alejandro Guizar resolved JBPM-1376.
------------------------------------
Fix Version/s: jPDL 3.2.4
SOA 4.2 CP02
Resolution: Done
Assignee: Alejandro Guizar
Made JbpmConfiguration.getInstance(String resource) not to throw an exception and emit a
warning instead. The warning only appears if a non-default resource name is specified.
Bug in JPDL 3.2.3 when using a configuration file not named
'jbpm.cfg.xml' (worked in 3.2.2)
--------------------------------------------------------------------------------------------
Key: JBPM-1376
URL: http://jira.jboss.com/jira/browse/JBPM-1376
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jPDL 3
Affects Versions: jPDL 3.2.3
Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13
Reporter: Joram Barrez
Assigned To: Alejandro Guizar
Fix For: jPDL 3.2.4, SOA 4.2 CP02
Attachments: ScriptExpressionTest.java
Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which
is not named 'jbpm.cfg.xml'.
See forum reference for more information and test class. Test class works for JPDL 3.2.2,
but not for 3.2.3.
Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should
not fail to start and use the standard config which is in the distribution.
--
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
1:43 a.m.
New subject: [JBoss JIRA] Closed: (JBPM-1376) Bug in JPDL 3.2.3 when using a configuration file not named 'jbpm.cfg.xml' (worked in 3.2.2)
[
https://jira.jboss.org/jira/browse/JBPM-1376?page=com.atlassian.jira.plug...
]
Alejandro Guizar closed JBPM-1376.
----------------------------------
Closing issues that I resolved in already released versions.
Bug in JPDL 3.2.3 when using a configuration file not named
'jbpm.cfg.xml' (worked in 3.2.2)
--------------------------------------------------------------------------------------------
Key: JBPM-1376
URL: https://jira.jboss.org/jira/browse/JBPM-1376
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.3
Environment: Windows XP, Eclipse 3.4, 0 JDK 1.6.0.05_b13
Reporter: Joram Barrez
Assignee: Alejandro Guizar
Fix For: jBPM 3.3.0 GA, SOA 4.2 CP02
Attachments: ScriptExpressionTest.java
Bug discovered when porting app from 3.2.2 to 3.2.3. Application uses a config file which
is not named 'jbpm.cfg.xml'.
See forum reference for more information and test class. Test class works for JPDL 3.2.2,
but not for 3.2.3.
Adding jbpm.cf.xml to the class path resolves the issue. However, by default jbpm should
not fail to start and use the standard config which is in the distribution.
--
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
5654
days inactive
5835
days old
4 comments
2 participants
participants (2)
-
Alejandro Guizar (JIRA) -
Joram Barrez (JIRA)