I guess I was focusing on the wrong thing. This is not a requirement of mine - nor have I had it arise. I've seen a couple of inquiries though, and I think people were tending toward the way I was trying to do it. I'll keep my eyes peeled 8-O for anyone else having this miconception.
ForwardAction actually does return an ActionForward now. It could be made contextRealtive very easily.
Ted Husted wrote:
Try using a "SuccessAction" that returns a real live ActionForward
return findForward("success");
with something like this
<forward name="success" path="http://jakarta.apache.org"; contextRelative="true"/>
and see if that gets you out.
The internal forward= action is already module/context relative. In 1.0, I had been using forward= inside the application and ForwardAction to get out.
Maybe ForwardAction should always be contextRelative, since it's stated purpose is to let us interact with other servlets, which implies it shouldn't understand modules at all.
I think there's another ticket in there about ForwardAction bypassing the RequestProcessor. May be it needs to create an ActionForward on the fly and set it to contextRelative=true, and then just return that.
I think a lot of people may be using ForwardAction when the ActionMapping.forward would be better suited, and maybe we need to clarify the difference.
I think ForwardAction is for hooking up with other servlets, applications, or domains, and ActionMapping.forward is for hooking up with other Struts resources in the same module, like JSPs.
-Ted.
-- Eddie Bush
-- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
