Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <18291680.1166148501686.JavaMail.jira@brutus>
Date: Thu, 14 Dec 2006 18:08:21 -0800 (PST)
From: "Greg Wilkins (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-2654) Enabling Welcome App (context
 "/") on geronimo-jetty6-jee5 assembly breaks web-console (context
 "/console")
In-Reply-To: <3763261.1165962321163.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-2654?page=comments#action_12458655 ] 
            
Greg Wilkins commented on GERONIMO-2654:
----------------------------------------

Oh - I see you also fixed the handler hierarchy.
I have just taken out the setServer calls and the 4 standard context run OK - there
are exceptions when stopping the server but I think they are unrelated (jdbc connections etc).

I haven't deployed the welcome app, but will check in anyway.

> 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