You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Sury Balasubramanian <su...@gaeaglobal.com> on 2008/06/10 19:30:58 UTC
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
Re: Websphere 6.1 and Struts 1.3
Posted by Struts Two <st...@yahoo.ca>.
I am running 1.3.10 on WAS 6.1 with no issues. Have installed the latest Websphere fixpacks and test.
However; if you struts version is 1.1 or 1.2, you may need to add the following property:
prependSlashToResource = true
to custom properties of your server.
--- On Mon, 4/5/10, Darshan Shroff <da...@infosys.com> wrote:
> From: Darshan Shroff <da...@infosys.com>
> Subject: Re: Websphere 6.1 and Struts 1.3
> To: user@struts.apache.org
> Received: Monday, April 5, 2010, 9:35 AM
>
> Hi,
>
> I am facing a similar issue. Any update on this. ?
>
> Regards,
> Darshan Shroff
> shroffdarshan@gmail.com
>
>
> newton.dave wrote:
> >
> > IIRC it's not necessary to use the extension when
> defining actions. That'd
> > actually kind of defeat one of the purposes of having
> a definable
> > extension.
> >
> >
> > --- On Tue, 6/10/08, Martin <mg...@hotmail.com>
> wrote:
> >
> >> From: Martin <mg...@hotmail.com>
> >> Subject: Re: Websphere 6.1 and Struts 1.3
> >> To: "Struts Users Mailing List" <us...@struts.apache.org>
> >> Date: Tuesday, June 10, 2008, 1:53 PM
> >> 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:
> >> user-unsubscribe@struts.apache.org
> >> For additional commands, e-mail:
> >> user-help@struts.apache.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
> >
>
> --
> View this message in context: http://old.nabble.com/Websphere-6.1-and-Struts-1.3-tp17760714p28138386.html
> Sent from the Struts - User mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
__________________________________________________________________
The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Websphere 6.1 and Struts 1.3
Posted by Darshan Shroff <da...@infosys.com>.
Hi,
I am facing a similar issue. Any update on this. ?
Regards,
Darshan Shroff
shroffdarshan@gmail.com
newton.dave wrote:
>
> IIRC it's not necessary to use the extension when defining actions. That'd
> actually kind of defeat one of the purposes of having a definable
> extension.
>
>
> --- On Tue, 6/10/08, Martin <mg...@hotmail.com> wrote:
>
>> From: Martin <mg...@hotmail.com>
>> Subject: Re: Websphere 6.1 and Struts 1.3
>> To: "Struts Users Mailing List" <us...@struts.apache.org>
>> Date: Tuesday, June 10, 2008, 1:53 PM
>> 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:
>> user-unsubscribe@struts.apache.org
>> For additional commands, e-mail:
>> user-help@struts.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Websphere-6.1-and-Struts-1.3-tp17760714p28138386.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Websphere 6.1 and Struts 1.3
Posted by Dave Newton <ne...@yahoo.com>.
IIRC it's not necessary to use the extension when defining actions. That'd actually kind of defeat one of the purposes of having a definable extension.
--- On Tue, 6/10/08, Martin <mg...@hotmail.com> wrote:
> From: Martin <mg...@hotmail.com>
> Subject: Re: Websphere 6.1 and Struts 1.3
> To: "Struts Users Mailing List" <us...@struts.apache.org>
> Date: Tuesday, June 10, 2008, 1:53 PM
> 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:
> user-unsubscribe@struts.apache.org
> For additional commands, e-mail:
> user-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Websphere 6.1 and Struts 1.3
Posted by Martin <mg...@hotmail.com>.
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: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org