I double checked the SVN trunk and the standard lifecycle stages seem to
look up the actionBean if they need it. From the test I remember doing
of this a few months ago, I recall it working fine when you create the
ActionBean and save it appropriately BEFORE the standard point where it
would have been created in the regular Lifecycle process. I cannot say
anything about replacing any existing ActionBean. That might be a
dangerous idea.
To review, it looks like the request attribute RESOLVED_ACTION stores
the string which is the key in the request scope which holds the current
ActionBean instance, unless you have @SessionScope set.
Regards,
David
Gérald Quintana wrote:
> Is it necessary to intercept all stages and do injection at each one?
> @Intercepts({LifecycleStage.ActionBeanResolution,
> LifecycleStage.HandlerResolution,
> LifecycleStage.BindingAndValidation,
> LifecycleStage.CustomValidation,
> LifecycleStage.EventHandling,
> LifecycleStage.ResolutionExecution,
> LifecycleStage.RequestInit,
> LifecycleStage.RequestComplete})
> public class GuiceInterceptor implements Interceptor {
>
> If the action injected the first time during action instanciation, and
> another time in the interceptor, isn't it a problem?
>
> Gérald
>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
