[ https://jira.jboss.org/jira/browse/JBPM-2501?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-2501: ----------------------------------- also revisit AcquireJobsCmd line 88 // if jboss is still booting exceptions that are due to improper // dependency configuration can be swallowed // https://jira.jboss.org/jira/browse/JBPM-2501 if (e.getMessage().indexOf("JbpmDS not bound")==-1) { throw e; } -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2501?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2501: ------------------------------ Original Estimate: 3 days Remaining Estimate: 3 days more background info in JBPM-2500 : "console should always use the jBPM configuration to fetch configurable properties " -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2501?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-2501: ----------------------------------- I want as much as possible in the jBPM codebase itself and as little as possible in the JBoss specific stuff. the goal is a clean JbpmService like this: public class JbpmService { private static final Log log = Log.getLog(JbpmService.class.getName()); private ProcessEngine processEngine; public void start() { this.processEngine = Configuration.getProcessEngine(); log.info("JbpmService started"); } public void stop() { this.processEngine.close(); log.info("JbpmService stopped"); } } * the JNDI name will be configured in the jbpm.cfg.xml * when a jBPM ProcessEngine is created, it checks for this JNDI name. if that is configured, it publishes itself in that location. that way the JNDI publishing and removal will be easier portable to other app servers. maybe we could even think of a similar .rar or .war deployment -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2501?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2501. ------------------------------- Resolution: Done -- 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