[JBoss jBPM] - rules engine, bpm, esb, msg'ing - functionality overlap?
by hanasakijiji
This is a business / architectural question - not necessarily a technical one.
Looking for a paper/whitepaper etc discussing how the three of these all work together in an enterprise environment.
As far as I can tell:
Messaging gives an implementation under the JMS API and perhaps an adapter to something like IBM MQ
|
| ESB gives webservices and often, not though not exclusively, a XML/SOAP layer on top of msg'ing. It also gives transformations, ACID transactions and a process flow (maybe session beans or maybe a scripting language like IBM broker)
|
| BPM gives a process flow with ACID transactions and a cool GUI for modeling the flow. A primary language used for BPM modeling is XML for BPEL
|
| A rules engine also models a business process. It can be a java lib called by a session bean or the rules can be exposed as webservices from their own 'container' like ILOG and others.
|
| So, what processes go in the rules engine? in BPM? In the ESB?
|
| When is it best to embed the rules code behind a sessionbean (maybe exposed as a WebService), called be the esb code? called by the bpm code? In a Rules container and centralized?
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000645#4000645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000645
19 years, 3 months
[JBoss Seam] - Component property class is not writable
by lowecg2004
Hi All,
I'm getting the following exception when I add a class attribute to s:link
java.lang.IllegalArgumentException: Component property class is not writable
| at javax.faces.component._ComponentAttributesMap.setComponentProperty(_ComponentAttributesMap.java:407)
| at javax.faces.component._ComponentAttributesMap.put(_ComponentAttributesMap.java:309)
| at com.sun.facelets.tag.jsf.ComponentRule$LiteralAttributeMetadata.applyMetadata(ComponentRule.java:49)
| at com.sun.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:36)
| at com.sun.facelets.tag.MetaTagHandler.setAttributes(MetaTagHandler.java:62)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:140)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:295)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:165)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
| at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
| at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
| at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:510)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:553)
| at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:178)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:326)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:290)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:213)
| at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:90)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:619)
If I remove the class attribute from the s:link then all is well, so clearly this is causing the problem.
Can s:link be modified to allow use of the class attribute? Or is there a good reason for it not being allowed?
Regards,
Chris.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000635#4000635
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000635
19 years, 3 months
[JBoss Messaging] - Re: MessageConsumer thread never goes away
by chip_schoch
I am not sure what JBM is but I am running jdk1.5.0_10, JBoss 4.0.5 GA, and Messaging 1.0.1GA. It would be difficult to post my actual code in this forum but it is essentially executing the following in the onMessage().
Properties p = new Properties ();
p.put (Context.PROVIDER_URL, "jnp://localhost:1099");
p.put (Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put (Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
InitialContext context = new InitialContext (p);
MessageConsumer consumer = null;
int count = 0;
Queue queue = (Queue) context.lookup (queuename);
try
{
consumer = jmssession.createConsumer (queue);
... do something here
]
consumer.close();
}
catch (Exception e)
{
System.err.println( "Exception while trying to clear error queue");
}
I verified that the createConsumer line is where the thread is being created and the thread remains when I undeploy my service. Each time a message goes through a new thread is created that never goes away.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000634#4000634
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000634
19 years, 3 months