[
http://jira.jboss.com/jira/browse/JBPM-761?page=all ]
Tom Baeyens closed JBPM-761.
----------------------------
Resolution: Rejected
With a simple code review I couldn't find see a problem. The SchedulerThread seems to
use the jbpmConfiguration parameter properly. I'm not going to spend more time to
look into this cause in 3.2, the scheduler and async messaging implementations are unified
and improved a lot. Please use one of the beta's we're going to release next
month to see of this problem is fixed in 3.2
SchedulerThread opens the default jbpm configuration (jbpm.cfg.xml)
even when created with a different config specification
---------------------------------------------------------------------------------------------------------------------------
Key: JBPM-761
URL:
http://jira.jboss.com/jira/browse/JBPM-761
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.1.2
Environment: Windows XP, JVM 1.4.2
Reporter: Michael Holtzman
Assigned To: Tom Baeyens
Priority: Minor
See jBPM forum
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=91756
Side issue: There is no way to instantiate org.jbpm.scheduler.impl.Scheduler with a
non-default jbpmConfiguration specification.
--
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