Spring MVC is taking a significantly different approach than Struts 2, as I understand it. Their OSGi support allows you to deploy a Spring MVC-based war into an OSGi container, while the Struts 2 plugin allows you to build part of your app as an OSGi bundle and deploy it in the embedded OSGi container. Therefore it goes like:
Spring MVC: OSGi container -> Tomcat -> war -> Spring MVC -> user code Struts 2: App server -> war -> Struts 2 -> OSGi plugin with embedded container -> Struts 2 bundles The difference is that Struts 2 will allow you to deploy your war on any existing app server, whether it supports OSGi or not. This also means a smoother migration process as you can leave your traditional Actions and templates in WEB-INF/lib, but deploy new Actions as bundles. Don On Thu, May 1, 2008 at 2:33 AM, Frans Thamura <[EMAIL PROTECTED]> wrote: > there are several topic about OSGI > > will S2 or S3 have osgi support > > which now i can see SpringMVC support it > > F > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]