I use Tiles and so all my forward actions look simply like this:
<action path="/home"
parameter="doc.moduleHome"
type="org.apache.struts.actions.ForwardAction"
scope="request">
</action>
Because doc.moduleHome is in the tiles-defs.xml for the current module it
looks nicer in the struts config.
That way, in the tiles-defs.xml you have the non module specific path listed
and so it will be of what you are looking for it sounds like. So in all my
tiles-defs.xml no matter if they are in the "main" module or in submodules
then I simply refer to any JSP as (in my case)
/WEB-INF/wherever/whatever.jsp You don't have to think about modules in the
tiles-defs.
You should think about using Tiles.
-----Original Message-----
From: Travis Stevens [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 2:40 PM
To: [EMAIL PROTECTED]
Subject: ForwardAction and modules
I have a module in which I have a forward action, and it seems that I
have to add the module name to the parameter of the forward page.
(actual example)
<action
path="/adminIndex"
parameter="/admin/adminIndex.jsp"
type="org.apache.struts.actions.ForwardAction"
/>
I would think that the ForwardAction should take into consideration
that the forward page is in the specified module:
(envisioned example)
<action
path="/adminIndex"
parameter="/adminIndex.jsp"
type="org.apache.struts.actions.ForwardAction"
/>
In my example there is an "admin" module and a file: /admin/adminIndex.jsp.
Any thoughts on this?
-Trav
---------------------------------------------------------------------
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]
