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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
