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