On Tue, 16 Nov 2004 12:39:09 -0500, Jeff Beal <[EMAIL PROTECTED]> wrote: > If you're using a basic hyper-link to switch from moduleA to moduleB, > you can use the module attribute of the <html:link/> tag to avoid all of > the SwitchAction rigamarole. (<html:link action="index" > module="moduleB">LINK TEXT</html:link> should do the trick) I don't > believe this will involve the request processor for moduleA in any way. > Unfortunately, the <html:form/> tag doesn't seem to have the module > attribute just yet.
Thanks for the reply. I can see where this might be useable in my app also. > > -- Jeff > > > > Susan Bradeen wrote: > > I have a Struts application that uses a custom request processor. Now > > I am trying to add a module so that I have part of the app using the > > standard request processor. The custom request processor makes checks > > on things I don't want checked when entering into my second module. Is > > it true that in order to switch modules from the original app (default > > module) to my second module, I am still making a pass through the > > default request processor, before forwarding to my second module? > > > > My understanding is that I put this in my default module struts-config: > > > > <action-mappings> > > <action path="/toModule" > > type="org.apache.struts.actions.SwitchAction"/> > > ... > > </action-mappings> > > > > Then, using the following I can switch to an action mapping listed in > > my second module: > > > > http://localhost:8080/toModule.do?prefix=/moduleB&page=/index.do > > > > However, since the switch action mapping is in the default module, > > that (switch) action is actually processed using the default module > > (custom) request processor. Am I correct on this? At least this is the > > behavior I appear to be seeing. So, if I am trying to avoid using this > > custom request processor to access features of my second module, then > > I need to go about this in a different way. Right? > > > > Hopefully my question is clear. Thanks for any input. > > Susan Bradeen > > --------------------------------------------------------------------- > 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]
