Hi Adam, On Fri, Aug 12, 2011 at 10:17 AM, <[email protected]> wrote: > [..] An application that cannot run in multiple spec-compliant > containers usually demonstrates problems with the codebase > (e.g. designing too much to implementation instead of to > contract, building independent versions of services that > ought to be contracted from the container, etc.).
Agreed. the same can be said when targeting servlet containers, collectively. Except in straight servlet container land, applications have more freedom (or "are saddled with more responsibility") to make decisions on typical appserver-level concerns. > 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. When Eddie and I looked at OSGi-ifying Fedora a while back, it certainly looked promising, but complex enough that we decided to back off and focus on Spring-ifying first. My memory is a bit fuzzy on the details, but I remember what I had *hoped* was that I could just write a webapp that would deploy anywhere, have an OSGi container running inside it, and be off to the races. It didn't seem quite that simple in practice. Also, back then the emergence of the Java Module System (Jigsaw) was a question. I found some recent news on that[1] which didn't seem all that encouraging. Do you know of any OSGi-based projects (whose source we can take a look at) that are designed to be deployed in multiple app servers *and* straight servlet containers? It would be very encouraging to know it's actually been done and we can see how. [1] http://mreinhold.org/blog/module-system-requirements > In the meantime, perhaps we can get some kind of a straw poll on > the users-list of sites either deploying or wanting to deploy Fedora > to something other than Tomcat or Jetty? Here are the results of a survey (with 31 responders) we did in January last year to support the decision to drop support for Java 5. https://jira.duraspace.org/browse/FCREPO-621 "Q2: Which app server(s) do you deploy with? 17 (55%) deploy with the bundled version of Tomcat 9 deploy with a non-bundled Tomcat 6.x (1 of those said they were moving toward JBoss) 5 deploy with a non-bundled Tomcat 5.5 4 deploy with a non-bundled Tomcat but did not specify a version" A new poll might be in order. > 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. +1 ...I'm very sensitive to putting any more demands on the already limited time we get from developers who work on Fedora today (whether they're officially committers or not). So the more hands we have helping with this stuff, the better. - Chris ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
