Don Brown wrote:
Technically, that isn't correct - PlugIn's are initialized once per
module, which may or may not be once per application.
Yes, good point, once per module, right.
But "may or may not be once per application"? This part I'm not as sure
about. The plugins, if memory serves. are called from init() of
ActionServlet (the call to initModulePlugIns() I think?)... so, they are
subject to loading and unloading of the servlet by the container, and
that can result in them being called more than once, true... Aside from
that possibility though, is there any other way a plugin could be called
more than once per application (and per module) startup? I didn't think so.
Eh, this isn't really all that important in the context of this
discussion anyway... I think the more cogent point is that I don't think
a plugin can be said to be analogous to a filter or interceptor, that's
my feeling anyway, and therefore there needs to be some analogy in SAF2,
whether something new or just a recommendation to use ContextListener
instead (which works just fine for me :) )
As for upgrading, I think converting a PlugIn to a context listener
would be pretty easy, so what I'm thinking would be better targets of
our work would be letting people use complex pieces like ActionForms
or JSP pages.
I think this is probably true... of course, you'd be missing the
referent to ActionServlet and ModuleConfig, but I agree, putting that
aside, the conversion probably isn't a big deal. I think recommending
conversion to ContextListeners is a perfectly reasonable response. That
would avoid entirely the possible double-execution caused by a servlet
reload as well, which is definitely better.
Are you planning to upgrade any legacy applications to Struts Action
2, and if so, what could we do to help?
See my other reply :)
Don
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
