Hiya Sacha. I agree that the MK can probably provide most of the required functionality but I believe we should be looking further out. We should be aiming the next release at the MC or OSGi frameworks (or even both). I am looking at both of these for a post GA task. You will not find anyone on the ESB team who disagrees with you about componentising the ESB. This is definitely important, especially if we are to obtain the ability to dynamically configure as much of the functionality as possible. As for configuration, ESB currently uses the TS property manager. This does not require the configuration file to be JVM-wide nor does it require the properties to be exposed via System properties. While doing this is possible with the TS property code it is usually not done unless some dependent jar requires it. I do not believe any of the ESB properties are exposed via System properties but I may be wrong. If they are then it should be a quick fix. It should, therefore, be straight forward to repackage the main ear/configuration file into a single exploded sar. Whether these jars can be further componentised at this time is really a question that only Esteban, Daniel, Kurt and Tom can answer. As far as the dependency on AS is concerned, that comment was really targetted at small form devices (such as mobile phones and PDAs) but also extends to other devices. I strongly believe we should be constructing the ESB using small, self contained plugins which remain as neutral as possible to the deployed environment. These plugins could then be combined as needed and, with an appropriate adapter layer, could then execute using the frameworks installed on the devices. If we are able to achieve this then I believe we will see the ESB being used in various configurations and devices which we have yet to consider. Kev View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988609#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...