> From: gildas.de.cadou...@gmail.com
> Date: Tue, 8 Jul 2014 12:36:14 +0200
> Subject: Re: dynamic interceptor insertion
> To: dev@struts.apache.org
>
> I look towards the ActionInvocation or ActionProxyFactory but the
> problem with this solution is that we do not know what Stack is
> executed.
MG> ValueStack ActionInvocation.getStack();
MG>?
MG>ActionProxyFactory
MG>ActionProxy createActionProxy(ActionInvocation actionInvocation, String
namespace, String actionName, String methodName,boolean executeResult, boolean
cleanupContext);
MG>save the actionInvocation
MG>when you need it reference the actionInvocation.getStack()
MG>?
> I also look towards a placeholder, but the problem is the same as previously.
>
> To clarify, my need: I want to allow the inclusion of a library in the
> classpath enable features brought by it without changing the
> configuration of the main project.
MG>perhaps inclusion of library as a <dependency> in your maven pom.xml would
satisfy this requirement?
>
> I hope you understand, because I know that my English is very bad (I'm french)
MG>Si les commentaires sont professionnels (vous obtiendrez toujours une
réponse polie)
MG>Bon Chance
> /**
> * Gildas de Cadoudal
> * 115, rue Mazarin
> * 33000 Bordeaux
> * (+33) (0)6 60 13 80 90
> * (+33) (0)9 50 15 62 40
> * gildas.de.cadou...@gmail.com
> **/
>
>
> On Thu, Jul 3, 2014 at 10:16 AM, Greg Huber <gregh3...@gmail.com> wrote:
> > What would be useful, if you could have a place holder in the interceptor
> > stack and then inject the interceptor element you need on the action?
> >
> > Copying the whole lot each time makes a lot more maintenance and more prone
> > to errors.
> >
> >
> > On 3 July 2014 02:32, Paul Benedict <pbened...@apache.org> wrote:
> >
> >> Most of the time, if not 99% of the time, all I want to do is add an
> >> interceptor before or after some known interceptor. As I've gone on record
> >> before, I want this feature too :-)
> >>
> >>
> >>
> >> Cheers,
> >> Paul
> >>
> >>
> >> On Wed, Jul 2, 2014 at 7:16 PM, Ken McWilliams <ken.mcwilli...@gmail.com>
> >> wrote:
> >>
> >> > Thank you Lukasz I'll put it on my todo list ;)
> >> >
> >> > Martin, interceptor stacks are efficient I think the scope struts2 has is
> >> > very good, still it is fun to push boundaries, one of those fun higher
> >> > initiatives would be a Web IDE for struts2. You could dynamically build
> >> an
> >> > interceptor stack, and you could step though the stack keeping an eye on
> >> > the action as part of the debug process, (values before and after
> >> > interceptor)...
> >> >
> >> > So in short no there isn't anything that can't be done with non dynamic
> >> > stacks, but in the name of learning this web framework and making things
> >> > more efficient- being able to dynamically alter the stacks is very
> >> > interesting. At the end the the day the idea was to write out a
> >> non-dynamic
> >> > struts.xml for production deployment.
> >> >
> >> >
> >> > On Wed, Jul 2, 2014 at 1:12 PM, Lukasz Lenart <lukaszlen...@apache.org>
> >> > wrote:
> >> >
> >> > > 2014-07-02 19:38 GMT+02:00 Ken McWilliams <ken.mcwilli...@gmail.com>:
> >> > > > This is somethings I've wanted to do (dynamically change the
> >> > interceptor
> >> > > > stack), I'm not at a development machine so have not checked the
> >> > > > plausibility of the following but would like input:
> >> > > >
> >> > > > Is it possible to create a custom ActionInvocation object, for this
> >> > > purpose?
> >> > > > Is it possible to essentially recreate the functionality of
> >> > > > ActionInvocation within an interceptor which then delegates to other
> >> > > > interceptors?
> >> > >
> >> > > Hm... yeah, with custom ActionInvocation and ActionProxyFactory should
> >> > > do the trick, check the REST Plugin to see what must be implemented to
> >> > > create your own ActionInvocation
> >> > >
> >> > >
> >> > > Regards
> >> > > --
> >> > > Łukasz
> >> > > + 48 606 323 122 http://www.lenart.org.pl/
> >> > >
> >> > > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> >> > > For additional commands, e-mail: dev-h...@struts.apache.org
> >> > >
> >> > >
> >> >
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
