[
http://jira.jboss.com/jira/browse/JBESB-447?page=comments#action_12355493 ]
Kurt Stam commented on JBESB-447:
---------------------------------
The pros are that deploying to JBossAS or to the JBM MC is pretty much doing the same
thing! So we end up with a simpler unified deployment strategy. In this standalone mode we
then support clean shutdowns, and clustering (which needs to be tested).
The downside is that ESB will be married to the 4.x MC for it's startup and shutdown
infrastructure. We would use no longer use the apache launcher. The ESB maybe persieved
heaver. Here is where it gets fuzzy for me. Would it still be light if we'd build our
own?
From a functionality perspective I think it's a no brainer that we
should do it. But keep in mind that what JBM is using is a fully dressed down (naked?)
version of JBossAS 4.x.
Make JBossESB 1.2.0GA the default JMS
-------------------------------------
Key: JBESB-447
URL:
http://jira.jboss.com/jira/browse/JBESB-447
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Configuration, Transports
Affects Versions: 4.0
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 4.0 Maintenance Pack 1
Now that JBoss Messaging has gone GA we should make it our default JMS provider.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira