On Fri, Jul 1, 2011 at 1:01 PM, Jean-Baptiste Onofré <[email protected]> wrote: > - ServiceMix as an embeddable WAR or EAR. Tomcat is just an example but the > purpose is wider. For my point of view, if we want to go this way, we > shouldn't be focus on Tomcat but be more generic. The purpose is to be able > to deploy ServiceMix 5 into existing containers like Tomcat, but also > Glassfish, Websphere, etc. The goals are to use the container resources > (JNDI, JTA, etc integration) and increase the ServiceMix adoption for > existing IT administrators.
Along those lines there are certainly some very interesting options. The industry really hasn't realized it yet and has only started to get it's head around some of the new tech, but basically the entire deployment model of Java EE got busted wide open. If you drop a META-INF/services/javax.enterprise.inject.spi.Extension file into a jar that is put into a WAR or EAR, you can quite literally participate in deployment and extend the app. And it's standard and usable in any server that supports CDI -- which is all certified Java EE 6 full or web profile servers. Users could write apps that have @Inject MyServiceMixThingy, and you could provide that standardly with all the existing hooks. You can even add new components, or even add your own dependency injection annotations or wrap the startup and shutdown of each and every component in the app. Frankly it's a little mind boggling. -David
