Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 56881 invoked from network); 15 Jul 2008 04:35:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jul 2008 04:35:56 -0000 Received: (qmail 2149 invoked by uid 500); 15 Jul 2008 04:35:55 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 2118 invoked by uid 500); 15 Jul 2008 04:35:55 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 2107 invoked by uid 99); 15 Jul 2008 04:35:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2008 21:35:55 -0700 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2008 04:35:01 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KIcG4-0000cn-B9 for dev@struts.apache.org; Mon, 14 Jul 2008 21:35:24 -0700 Message-ID: <18457942.post@talk.nabble.com> Date: Mon, 14 Jul 2008 21:35:24 -0700 (PDT) From: alvins To: dev@struts.apache.org Subject: Re: [s2] Struts 2 OSGi Plugin In-Reply-To: <1c661f2f0807142018n503be7e6r97950706109977c9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: alvins1982@hotmail.com References: <436d9a250707290742i4d4aaa67ibbd991f4140591eb@mail.gmail.com> <46ACAAF4.8030406@omnytex.com> <436d9a250707291702p6ee3b0ake72cc85ea47ba6c4@mail.gmail.com> <18415829.post@talk.nabble.com> <1c661f2f0807112351n6eef6ebduba97439c80009658@mail.gmail.com> <18435680.post@talk.nabble.com> <436d9a250807132245l25ac3e54vfeeea4283ae289b@mail.gmail.com> <18457332.post@talk.nabble.com> <1c661f2f0807142018n503be7e6r97950706109977c9@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Ahh i see. The reason I can see that people would really want it is the transition to OSGi would be less painful. People don't want to do too much rewriting. So far to move to OSGi it is not too difficult and does not require too much change to an existing project. But if there is no JSP support it will prove quite difficult and will be difficult to get buy-in initially I think. Alvin Don Brown wrote: > > The key problem is JSP files cannot be packaged in a JAR, which is the > default format of a bundle. The way systems like Sling and Spring > Application Platform get around it is by embedding a Tomcat or Jetty > instance within the OSGi container, then adding OSGi headers to the > war manifest and deploying it as an OSGi bundle. The hybrid approach > taking by the OSGi plugin puts an OSGi container in an existing > webapp, but doesn't try to run a second application server in OSGi > space, therefore JSP's won't work without significantly modifying a > JSP compiler, and besides, Sun has basically deprecated JSP's in favor > of JSF and even replacing JSP with Facelets in JSP 2.0. Velocity or > Freemarker templates are so much easier to develop, test, and debug, > so I don't really see the loss. > > Don > -- View this message in context: http://www.nabble.com/-s2--Struts-2-OSGi-Plugin-tp11851951p18457942.html Sent from the Struts - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org