More on this:

Entering http://localhost:8080/ExpenSysWT/help.do?context=LOGIN_PAGE (the
correct path to the action) manually in the address field produces the 500
error when the login page is first displayed. After the user has logged in
it works fine.

I don't understand if its the Tomcat config or is the Struts config. I would
have thought that if its Tomcat it would never work.....


TIA - Adam




-----Original Message-----
From: Jim Barrows [mailto:[EMAIL PROTECTED] 
Sent: 29 June 2004 20:03
To: Struts Users Mailing List
Subject: RE: NEWBIE: Wierd problem - Action sometimes produces Status 500 -
No Context configured to process this request


This almost sounds like the action is getting executed at all, but is rather
a problem with the server setup.  Context usually refers to everything up to
and including the app name, so that would make sense if there's a server
configuration issue. If it is executing the action, then at what point is
the 500 being thrown?

> -----Original Message-----
> From: Adam Lipscombe [mailto:[EMAIL PROTECTED]
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
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]

Reply via email to