[ http://issues.apache.org/jira/browse/GERONIMO-2654?page=comments#action_12458661 ] Greg Wilkins commented on GERONIMO-2654: ----------------------------------------
The 500 responses in the tests are because the ContextHandlerCollection sends a 500 if it has not contexts configured. I am not sure why that is and I will probably change it. However, for now it is indicated that the tests worked as well as the 404. So I will change the tests to expect 500 - and for the next release of Jetty we will probably have to change back to 404s > Enabling Welcome App (context "/") on geronimo-jetty6-jee5 assembly breaks > web-console (context "/console") > ----------------------------------------------------------------------------------------------------------- > > Key: GERONIMO-2654 > URL: http://issues.apache.org/jira/browse/GERONIMO-2654 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Jetty > Affects Versions: 2.0-M1 > Environment: Windows XP ... most likely all. > Reporter: Joe Bohn > Assigned To: Greg Wilkins > > There seems to be something strange going on with context resolution. When > the welcome application is enabled on the jetty6-jee5 assembly (update > config.xml and remove load="false" for webconsole-jetty6) the welcome > application works fine (context "/"). However, it appears that all other > applications, such as the web console (context "/console") are no longer > accessible and return 404 errors when attempting to access the application > from a browser. > This may actually be a Jetty 6.1 problem rather than a Geronimo problem. > David Jencks recommended looking into Jetty's ContextHandlerCollection > class for clues as to what is happening. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
