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 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]
