What about using a different class to host the ThreadLocal?
public void pojoActionMethod() {
ActionContext ctx = ActionContextHolder.getActionContext(); if (...) { ctx.setForwardConfig(ctx.getMapping().findForward("a")); } else { ctx.setForwardConfig(ctx.getMapping().findForward("b")); } }
It seems arbitrary to me, and more of a burden than simply having a public static ThreadLocal which most people would ignore -- but if others prefer this approach, I wouldn't fight it.
The instance would be set by the RequestProcessor at the start of the chain after the context is created.
Yes, no matter where we store the ActionContext, my intent would be to set this in process() right after contextInstance(...).
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
