To be honest, I don't know. But, what makes the s2/osgi different from other OSGi integration libraries is that bundles are deployed within the single web-app. This means, you could create one bundle with your "base" actions and then deploy other bundles without restarting your app.
I could be completely off-base, I wasn't involved with writing the plugin, I am just trying to regurgitate memories from the discussion on [EMAIL PROTECTED] Maybe Musachy can chime in. -Wes On Tue, 2008-11-18 at 14:00 -0600, Relph,Brian wrote: > That plugin looks promising, the isolated classpaths requirement could be > bent ... > > Does the plugin require that all actions be loaded from bundles? > > Brian Relph > > -----Original Message----- > From: Wes Wannemacher [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 18, 2008 10:18 AM > To: Struts Users Mailing List > Subject: Re: [S2] Plugin architecture > > I am not sure if it does exactly what you want (isolated classpaths), but > this might help get you started - > > http://cwiki.apache.org/S2PLUGINS/osgi-plugin.html > > Note, this plugin is experimental and hasn't seen updates in a while, but > still worthwhile. > > -Wes > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
