"kurt.stam(a)jboss.com" wrote : As Daniel already said we will soon have 3 jars, and no longer an ear. This codebase does not necessarely need a AS at this point, however it does need an (external) JMS provider. In my opinion we have the following options: | | 1. deploy the jars to the AS, the ESB is a app on top of the AS | 2. start the ESB by itself with a small bootstrapper, the ESB is an app by itself. After GA we will need the MK in there to support all we need on the roadmap. | 3. support both ways of running the ESB. | | We have been moving towards option 2, the thing left to do is the little bootstrapper and start scripts in my opinion. Historically this is the way rosetta has been running with listeners runnning as 'adapter' on the various systems, talking to one central host. These listeners reread their configuration periodically. | | It would be nice if we can agree on a packaging that would get us to option 3 in my option. | | --Kurt There are two separate issues here: (i) how to package and configure the 4.0 GA. We've agreed that we need some wizards to help with this. I think there are at least two requirements/wizards here: how to run the ESB within an application server and how to run it stand-alone. If we can simplify the out-of-the-box experience for both of these for the GA then I think we'll satisfy many/most users of the GA. (ii) how to package and configure the 5.0 GA (next release). As this discussion as pointed out, things will change when we support MC. Furthermore, feedback from (i), both from implementing the wizards and eventually/hopefully from users, will influence this. Although we can/should definitely continue to discuss (ii), it can't be at the detriment of (i). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988746#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...