[Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss
by bill.burke＠jboss.com
"camunda" wrote :
| I like the protability of jBPM very much. And I think it is a important advantage that should be kept. Today it runs in standalone, Tomcat, JBoss or other AS environments. Very important in my eyes. So some proprietary JBoss deployment should be always (or at least in the near future) additional. Thats what the people like about jBPM, it is not tied to some AS.
|
A couple of things:
* I never talked about removing the current way of jBPM deployment
* Portability is good. BUT...many developers use more than one JEMS project. Wouldn't it be good if deployment was portably consistent between desparate projects? This is why I created the http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedJBoss project.
* I don't think jBPM can continue to live in a black box in terms of versioning. jBPM interacts with web applications and various other subsystems that would also need to be versioned. How do current jBPM users handle this scenario?
Many JBoss.org projects like jBPM have done a great job at being portable to other environments than JBoss AS. Unfortunately, they have not done a great job at taking advantage of the JBoss AS platform and becoming a cohesive suite of projects. Right now, most JBoss.org projects are configured and deployed different and have their own unique, but similar/familiar component models. When you want to use two of these projects together, it becomes painful. Tooling efforts are more difficult. An overall way of tieing these projects together is non-existent. This is what I'm trying to solve. We need to get to a point where 1 + 1 > 2.
The funny thing is, JBoss AS has the opposite problem, it looks like one product, but does a horrible job at running in other environments.
The thing is, I NEED INPUT from users like yourself. I'm trying to figure out the big picutre. How all these projects at JBoss.org can fit together. Learning how you all use these projects alone or together is part of the process. Please help!
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053575#4053575
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053575
19 years
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p
by timfox
Here's the default (local) JMSProviderLoader from jms-ds.xml:
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
| <!-- Uncomment to use HAJNDI to access JMS
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=localhost:1100
| </attribute>
| -->
| </mbean>
|
You should just be able to set one up pointing to your ActiveMQ instance and reference that as your target JMSProviderLoader in the bridge config.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053566#4053566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053566
19 years