Norm,
It has changed because we were using a container-specific mechanism to override the default context (which is name of webapp war or dir) by specifying a context name in the jetty-config.xml file. We want to move away from these plugin-specific config files. Therefore, the only ways to configure an alternate context name for a webapp (in a non-Jetty/Tomcat/etc specific manner) are:
1. in a Geronimo web.xml descriptor 2, in an application.xml descriptor
The handling of Geronimo deployment descriptors is very much in the early days, although we are making progress to being able to deploy an ear/war etc containing Geronimo deployment descriptors. So hang on to your shorts 'cause option 1 will be coming along in the near future.
As the console isn't in an ear, then option 2 is a non starter.
In the short term, if you really want the context path to be /console, then you could just rename the war to console.war.
cheers, Jan
n. alex rupp wrote:
I'm curious why you moved it from "console" to "geronimo-web-console"?
It seems to me (which is why we renamed it from jmx-console) that "geronimo" and "web" are pretty redundant, considering you're typing the URL into a web browser on the Geronimo server. But maybe there's something I'm missing (wouldn't be the first time : )
In any case, if you could briefly touch upon this, I'd be very grateful.
-- N. Alex Rupp
----- Original Message ----- From: "Jan Bartel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 06, 2003 7:21 AM
Subject: [web deployment] Default Jetty deployment
FYI,
I have changed the Jetty runtime deployer from the so-called "hack" Jetty integration to the "official" Jetty integration. Webapps will now deploy by dropping a war into the target/geronimo-DEV/deploy directory.
For users of the Geronimo web management console, please note that at least for now, it will now be available at url http://localhost:8080/geronimo-web-console instead of http://localhost:8080/console.
Jan
