[JBoss Seam] - Re: jBPM integration question
by fady.matar
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
18Â years, 10Â months
[JBoss Seam] - seam-generated ear: IncompatiblaClassChangeError
by dajevtic
Hi, folks! First of all I really want to thank everyone involved in this project for making such an effort in making Seam my first Application Framework of choice. I really enjoy the hours I spend in learning more and more about Seam.
Now to the bad part ;-)
Today I updated from CVS version and from now on my newly created web apps give me following WARNing everyime I access a page:
anonymous wrote : 22:31:45,358 WARN [lifecycle] phase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@2933dc) threw exception: java.lang.IncompatibleClassChangeError null
| org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:331)
| org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:83)
| org.jboss.seam.jsf.SeamPhaseListener.afterRender(SeamPhaseListener.java:515)
| org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:230)
| org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184)
| com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280)
| com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
| org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:62)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
| org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40)
| org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
| org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| java.lang.Thread.run(Thread.java:595)
|
Any idea if this is a temporary "flaw" or if my app server's settings (I changed quite a few) are not compatible with the 1.3 version of seam?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057211#4057211
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057211
18Â years, 10Â months