Re: Switching Modules and Request Processors

2004-11-16 Thread Susan Bradeen
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 tag to avoid all of > the SwitchAction rigamarole. ( module="moduleB">LINK TEXT should do the trick) I don't

Re: Switching Modules and Request Processors

2004-11-16 Thread Susan Bradeen
On Tue, 16 Nov 2004 12:22:08 -0500, Bill Siggelkow <[EMAIL PROTECTED]> wrote: > I believe your observations are correct. If you want to avoid the > "special features" you could conditionally skip them if the request is a > SwitchAction to the new module ... just one idea. > Ok, thanks for the c

Re: Switching Modules and Request Processors

2004-11-16 Thread Jeff Beal
If you're using a basic hyper-link to switch from moduleA to moduleB, you can use the module attribute of the tag to avoid all of the SwitchAction rigamarole. (LINK TEXT should do the trick) I don't believe this will involve the request processor for moduleA in any way. Unfortunately, the

Re: Switching Modules and Request Processors

2004-11-16 Thread Bill Siggelkow
I believe your observations are correct. If you want to avoid the "special features" you could conditionally skip them if the request is a SwitchAction to the new module ... just one idea. Susan Bradeen wrote: I have a Struts application that uses a custom request processor. Now I am trying to

Switching Modules and Request Processors

2004-11-16 Thread Susan Bradeen
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 ord