> I'd like to suggest a different route, one already formally endorsed by > Fedora. Moving the application to the OSGi framework will enable it to be > deployed in almost any container (including many totally off the JEE specs), > helped by the clean, stringent OSGi classloading architecture. It's an > enormous amount of work to be done, certainly, but I'd suggest that it will > be work of more lasting benefit than constructing in-project machinery to > support multiple containers.
+1, for sure. > There might be some simple ways to help the community support itself without > investing a lot of committer time in the effort. If one site has good schemes > for this kind of deployment that aren't too onerous, that might be very > helpful to start. Right. In the link I posted yesterday, the jboss community seems to have acknowledged that dependencies in wars that conflict with container provided artifacts is a common problem, and there are some configuration-based workarounds. I'm sure we could collect stories of what works and what doesn't. -Aaron ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Fedora-commons-developers mailing list Fedora-commons-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
