You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Barett McGavock <bm...@pulvertech.com> on 2004/06/29 21:17:02 UTC
RE: NEWBIE: Wierd problem - Action sometimes produces Status 500
- No Context configured to process this request
I think you're on the right track with your idea that no action has run
first. Usually in Struts an action should run before the JSP is seen.
Does it work if you use the following tag on your index.jsp instead?
<logic:redirect forward="/login"/>
B
> -----Original Message-----
> From: Adam Lipscombe [mailto:adam.lipscombe@expensys.com]
> Sent: Tuesday, June 29, 2004 10:31 AM
> To: 'Struts Users Mailing List'
> Subject: NEWBIE: Wierd problem - Action sometimes produces
> Status 500 - No Context configured to process this request
>
>
> Folks,
>
>
> I have a strange problem that is confusing me:
>
> I have a simple login page with a Help button defined like this:
>
> <html:link href="javascript:displayHelp('loginPage')"%>"<img
> border="0" height="28" name="Image10"
> src="images/b_help_1.gif" width="32"></html:link>
>
>
> When pressed, the JavaScript displayHelp() method below is called:
>
> function displayHelp(context)
> {
> [snip]
>
> var url = "<html:rewrite page='/help.do' />"
> url += "?context=" + context;
>
> [snip]
>
> window.open(url, "HelpWindow", windowOptions);
> }
>
>
>
> This page is the first page that the user sees, having been
> redirected from index.jsp like this:
>
> <logic:redirect forward="login"/>
>
>
>
>
> The problem is that before a user logs in, pressing the
> "Help" button results in the error "HTTP Status 500 - No
> Context configured to process this request" being displayed.
>
> However after a user logs in (and presses the browser back
> button to return to the login page) the link works fine and
> the help is displayed OK.
>
>
> Its as if the act of logging in sets up a context within
> which the actions work....
>
>
>
> The relevant bits of my struts-config looks like this:
>
> <global-forwards>
> <forward name="login" path="/pages/Login.jsp" />
> </global-forwards>
>
> <action-mappings>
> <action input="/pages/Login.jsp" name="loginActionForm"
> path="/login" scope="request"
> type="com.expensys.expensyswt.struts.action.Login"
> validate="true">
> <forward name="home" path="/pages/Home.jsp" />
> </action>
>
> <action path="/help" scope="request"
> type="com.expensys.expensyswt.struts.action.DisplayHelp"
> validate="false" >
> <forward name="loginHelp" path="/pages/help/LoginHelp.jsp" />
> <forward name="displayHelpTopics"
> path="/pages/help/HelpTopics.jsp" /> </action> </action-mappings>
>
>
>
> Does anyone know what is going on here?
> Why does the "/help.do" action URL work after the user has
> logged in but not before?
> Is it to do with the fact that no action has been called
> before the log in takes place?
>
>
>
> TIA - Adam
>
>
>
> ---------------------------------------------------------------------
> 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: NEWBIE: Wierd problem - Action sometimes produces Status 500 - No Context configured to process this request
Posted by Adam Lipscombe <ad...@expensys.com>.
Thanks Barett,
Its true that no action runs. Tomcat displays "MAPPING configuration error
for request URI" when the 500 error is generated.
But why does it work once the user has logged in?
If I change the initial redirect to "/login" it fails with the following
displayed in the browser window:
javax.servlet.ServletException: Cannot create redirect URL:
java.net.MalformedURLException: Cannot retrieve ActionForward named /login
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:463)
at org.apache.jsp.index$jsp._jspService(index$jsp.java:91)
[snip]
Hmm, guess I will have to look at the Tomcat config. Its odd that it starts
working OK when the user is logged in.
TIA - Adam
-----Original Message-----
From: Barett McGavock [mailto:bmcgavock@pulvertech.com]
Sent: 29 June 2004 20:17
To: 'Struts Users Mailing List'
Subject: RE: NEWBIE: Wierd problem - Action sometimes produces Status 500 -
No Context configured to process this request
I think you're on the right track with your idea that no action has run
first. Usually in Struts an action should run before the JSP is seen.
Does it work if you use the following tag on your index.jsp instead?
<logic:redirect forward="/login"/>
B
> -----Original Message-----
> From: Adam Lipscombe [mailto:adam.lipscombe@expensys.com]
> Sent: Tuesday, June 29, 2004 10:31 AM
> To: 'Struts Users Mailing List'
> Subject: NEWBIE: Wierd problem - Action sometimes produces
> Status 500 - No Context configured to process this request
>
>
> Folks,
>
>
> I have a strange problem that is confusing me:
>
> I have a simple login page with a Help button defined like this:
>
> <html:link href="javascript:displayHelp('loginPage')"%>"<img
> border="0" height="28" name="Image10"
> src="images/b_help_1.gif" width="32"></html:link>
>
>
> When pressed, the JavaScript displayHelp() method below is called:
>
> function displayHelp(context)
> {
> [snip]
>
> var url = "<html:rewrite page='/help.do' />"
> url += "?context=" + context;
>
> [snip]
>
> window.open(url, "HelpWindow", windowOptions);
> }
>
>
>
> This page is the first page that the user sees, having been
> redirected from index.jsp like this:
>
> <logic:redirect forward="login"/>
>
>
>
>
> The problem is that before a user logs in, pressing the
> "Help" button results in the error "HTTP Status 500 - No
> Context configured to process this request" being displayed.
>
> However after a user logs in (and presses the browser back
> button to return to the login page) the link works fine and
> the help is displayed OK.
>
>
> Its as if the act of logging in sets up a context within
> which the actions work....
>
>
>
> The relevant bits of my struts-config looks like this:
>
> <global-forwards>
> <forward name="login" path="/pages/Login.jsp" />
> </global-forwards>
>
> <action-mappings>
> <action input="/pages/Login.jsp" name="loginActionForm"
> path="/login" scope="request"
> type="com.expensys.expensyswt.struts.action.Login"
> validate="true">
> <forward name="home" path="/pages/Home.jsp" />
> </action>
>
> <action path="/help" scope="request"
> type="com.expensys.expensyswt.struts.action.DisplayHelp"
> validate="false" >
> <forward name="loginHelp" path="/pages/help/LoginHelp.jsp" />
> <forward name="displayHelpTopics"
> path="/pages/help/HelpTopics.jsp" /> </action> </action-mappings>
>
>
>
> Does anyone know what is going on here?
> Why does the "/help.do" action URL work after the user has
> logged in but not before?
> Is it to do with the fact that no action has been called
> before the log in takes place?
>
>
>
> TIA - Adam
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org