How hard would it be to "allow for" struts run time configuration? In allowing for I mean having a registry for the configuration of interceptor stacks, packages, actions... which the framework will allow for querying and in the default case would be immutable but would allow us to substitute in mutable managers for these configuration services? One use-case is to produce a struts2(struts3) IDE which runs in a browser.
On Mon, Nov 26, 2012 at 1:24 PM, Dave Newton <[email protected]> wrote: > I have no problem with that. (Obviously ;) > > IMO the S1 plugin was never anything more than a stopgap measure; > since JSPs had to be rewritten anyway it was more of a temporary > solution during migration. > > Dave > > On Mon, Nov 26, 2012 at 3:21 PM, Lukasz Lenart <[email protected]> > wrote: > > 2012/11/22 Lukasz Lenart <[email protected]>: > >> 2012/11/22 Dave Newton <[email protected]>: > >>> How useful is the Struts 1 plugin? > >> > >> It's mentioned as a migration way for S1 projects, but we can drop > >> support for S1 in S3 > > > > Any thoughts? I'm almost sure that we should drop support for S1 in S3 > > and used org.apache.struts as a base package name. > > > > > > Regards > > -- > > Łukasz > > + 48 606 323 122 http://www.lenart.org.pl/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > e: [email protected] > m: 908-380-8699 > s: davelnewton_skype > t: @dave_newton > b: Bucky Bits > g: davelnewton > so: Dave Newton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
