Dear Steve,
Thanks for finding the problem in the configuration file. I had
not realized it. ** sorry for the typo in bug report **
So, now I have an enhancement request.. :)
Would it be possible to enhance ForwardAction so that it also
requires a MODULE relative path ?
It would be then very intuitive and convenient.
Also, splitting into modules will be easier as you simply have to
chop off the module path globally. Changing module names will be
even easier.
If you think the above is ok and it doesnt conflict with the current
implementation, I shall re-open the bug as an enhancement request.
Please let me know,
Thanks a bunch,
Ajay
Ajay,
I've closed this bug. It seems to be a configuration problem...
I'm assuming that your add.jsp and edit.jsp files are in the /admin
directory.
The problem is with your configuration. ForwardAction requires a CONTEXT
relative path which, in this case would be:
<action path="/showEdit"
type="org.apache.struts.actions.ForwardAction"
parameter="/admin/edit.jsp">
</action>
(Note also, you had your parameter in a separate tag, but it should be
an
attribute of the action tag. Not sure if that's what you actually had in
your
source or it's just a typo in the bug report, but it wouldn't help!)
The reason it worked when you used your own custom action is that by
default
ActionFoward paths are MODULE relative, so your configuration entry
"/edit.jsp"
would be translated by the RequestProcessor to a context relative path
of
"/admin/edit.jsp"
... if you still have problems after this, please post back to the user
list.
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
