struts-config.xml
<action-mappings>
<!-- Default "admin" action -->
<!-- Forwards to com.schpro.action.AdminAction -->
<action path="/admin" type="com.schpro.action.AdminAction">
<forward name="configure" path="/jsp/admin.jsp" />
<forward name="projectsearch" path="/projectsearch.do" />
</action>
you have admin defined as path instead of 'admin.do'
Martin
----- Original Message -----
From: Sury Balasubramanian
To: user@struts.apache.org
Sent: Tuesday, June 10, 2008 1:30 PM
Subject: Websphere 6.1 and Struts 1.3
Hello all,
I am having an issue with a webapp developed on struts 1.3 on Websphere
6.1.07 (running on AIX). The webapp when compiled, tested and run on Windows
(websphere 6.1.015) works fine. The problem is as follows. The application
installs properly. If i login and directly access a JSP i don't have an issue
at all. If I use a url
http://<server>:<port>/sp/admin.do (struts url). Users get the following
error:
"Error 404: Parsing error processing resource path
/WEB-INF/struts-config.xml"
The following files are attached:
web.xml
struts-config.xml
trace on websphere when the struts request is sent
The following were already checked:
struts.xml is referred to with a leading slash /WEB-INF/struts.xml in the
web.xml as prescried by IBM.
the server property of leading slash is also set to make sure we read the
leading slash.
Is this a good place to post this or on the websphere forum? Is there
something missing on the config.xml that websphere specifically validates?
Thanks
Sury
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
