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 On Tue, Jul 15, 2008 at 1:12 PM, alvins <[EMAIL PROTECTED]> wrote: > > I would think JSP support would have to be mandatory for wide acceptance?? I > know in the alpha plugin you are using is Apache Felix as the OSGi container > but Equinox is building in JSP support (they also have a struts example) - > http://www.eclipse.org/equinox/server/jsp_support.php. > > > Don Brown-2 wrote: >> >> It all depends on the approach. Currently, JSP's aren't supported and >> in fact, I doubt they will ever be supported. If tiles can work with >> Freemarker or Velocity, then I don't see why we couldn't get it >> working. >> >> Don >> > > -- > View this message in context: > http://www.nabble.com/-s2--Struts-2-OSGi-Plugin-tp11851951p18457332.html > Sent from the Struts - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
