You can also opt for sharing the prepare() code through inheritance, meaning that you create a superclass action holding the prepare() code, instead of coding a custom interceptor.
2008/7/11 Andreas Mähler <[EMAIL PROTECTED]>: > Thanks for your Answer, Lukasz. > > I already know the PrepareInterceptor and it can be used for what I would > like to do. But I consider a special interceptor more convinient, since I > intend to use it for more than one pair of view and action. (Using > PrepareInterceptor would imply the need to add the code to every single > action.) > > In my original post, i was wondering if there already is some kind of > "recipe"/"best practice"/"standard way" since I don't think that my wish to > put the actions together is very exotic. > > But as nobody intervened I take this as a sign that my design is not flawed > :-)) > > See You! > ~Andreas > > > Lukasz Lenart schrieb: >> >> Check PrepareInterceptor [1] with prepare() method >> >> [1] http://struts.apache.org/2.1.2/docs/prepare-interceptor.html > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
