Now this approach does not work out anymore since I upgraded from CVS to version 1.3.0.BETA1
@Interceptor(NEVER) is no longer there because of a change in API. I have created my modification as follows and still the jbpm database is not being deployed automatically without having any process definition or page flow declared. | package org.jboss.jbpm.console.console; | | import org.jboss.seam.annotations.Install; | import org.jboss.seam.annotations.Logger; | import org.jboss.seam.annotations.Name; | import org.jboss.seam.annotations.Startup; | import org.jboss.seam.annotations.intercept.Interceptor; | import org.jboss.seam.bpm.Jbpm; | import org.jboss.seam.log.Log; | | import static org.jboss.seam.annotations.intercept.InterceptorType.ANY; | | @Interceptor(type = ANY) | @Name("org.jboss.console.bpm.init") | @Startup(depends = { "org.jboss.seam.bpm.jbpm" }) | @Install(dependencies = "org.jboss.seam.bpm.jbpm") | | public class JbpmInitializer extends Jbpm { | | @Logger | Log log; | | /** | * Startup method to start the jbpm context | */ | public void startup() throws Exception { | super.startup(); | if (getProcessDefinitions() == null | || getProcessDefinitions().length < 1) { | try { | log.debug("Starting up jBPM"); | getJbpmConfiguration().createJbpmContext().getContextSession(); | log.debug("jBPM initialized"); | } catch (Exception e) { | log.error("jBPM Initialization Exception: " + e.getMessage()); | e.printStackTrace(); | } | } | } | } | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057213#4057213 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057213 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user