Re: Changes to server started messages
I think it makes more sense w/o the full url bits, since those are highly dependent on how you configured the connectors. --jason On Aug 2, 2007, at 6:25 PM, Jeff Genender wrote: Yup... The old messages made no sense at all...because Web application != connector and therefore its not fair to determine that the web applications actually listen on http. In long discussions with David Jencks, we agreed the slapping of http in from of the URL was purely a hack and was not correct for complex cases...i.e. the applications you listed also are running on https *and* ajp. In otherwords, the web application is independent of the scheme (http) and it shouldn't know its own scheme. It *is* correct for the web application to know it's identified by the context, and thats why you see them listed. I hope this made sense. Jeff Kevan Miller wrote: I noticed that the server started messages have changed. The started Web Applications are now of the following form: Web Applications: / /console /console-standard /dojo /remote-deploy Geronimo Application Server started Where they used to be: Web Applications: http://coltrane:8080/ http://coltrane:8080/console http://coltrane:8080/console-standard http://coltrane:8080/dojo http://coltrane:8080/remote-deploy Geronimo Application Server started I'm assuming that this is associated with the recent Connector changes... I preferred the old messages, but I doubt I'll lose very much sleep... Apologies if I missed discussion about this. Even more apologies if the network config on my machine has gone bonkers... ;-) --kevan
Re: Changes to server started messages
On Aug 6, 2007, at 4:24 AM, Jason Dillon wrote: I think it makes more sense w/o the full url bits, since those are highly dependent on how you configured the connectors. Ya. I understood that when I asked. And don't necessarily disagree with where we end up. We might consider tweaking the startup message a bit. Two points: 1) Discuss/document the decision on [EMAIL PROTECTED] If it was discussed/ documented on dev@, then my apologies... 2) Note that http://localhost works just perfectly for umpity percent of users. So, we've sacrificed some usability for some accuracy. We're accurate for more complex cases where users know how to change our default connectors (most of whom would understand the relativity of the app contexts, anyway). And we're less usable for naive users (e.g. ones who just downloaded Geronimo for the first time). --kevan
Re: Changes to server started messages
I guess the startup screen need not list all possible URLs to access each application. One per app should be good enough for the user to quick start. Easy to use is our first guiding principle. We will not want a user to struggle finding out the URL of welcome app!!! Vamsi On 8/6/07, Kevan Miller [EMAIL PROTECTED] wrote: On Aug 6, 2007, at 4:24 AM, Jason Dillon wrote: I think it makes more sense w/o the full url bits, since those are highly dependent on how you configured the connectors. Ya. I understood that when I asked. And don't necessarily disagree with where we end up. We might consider tweaking the startup message a bit. Two points: 1) Discuss/document the decision on [EMAIL PROTECTED] If it was discussed/ documented on dev@, then my apologies... 2) Note that http://localhost works just perfectly for umpity percent of users. So, we've sacrificed some usability for some accuracy. We're accurate for more complex cases where users know how to change our default connectors (most of whom would understand the relativity of the app contexts, anyway). And we're less usable for naive users (e.g. ones who just downloaded Geronimo for the first time). --kevan
Re: Changes to server started messages
Yup... The old messages made no sense at all...because Web application != connector and therefore its not fair to determine that the web applications actually listen on http. In long discussions with David Jencks, we agreed the slapping of http in from of the URL was purely a hack and was not correct for complex cases...i.e. the applications you listed also are running on https *and* ajp. In otherwords, the web application is independent of the scheme (http) and it shouldn't know its own scheme. It *is* correct for the web application to know it's identified by the context, and thats why you see them listed. I hope this made sense. Jeff Kevan Miller wrote: I noticed that the server started messages have changed. The started Web Applications are now of the following form: Web Applications: / /console /console-standard /dojo /remote-deploy Geronimo Application Server started Where they used to be: Web Applications: http://coltrane:8080/ http://coltrane:8080/console http://coltrane:8080/console-standard http://coltrane:8080/dojo http://coltrane:8080/remote-deploy Geronimo Application Server started I'm assuming that this is associated with the recent Connector changes... I preferred the old messages, but I doubt I'll lose very much sleep... Apologies if I missed discussion about this. Even more apologies if the network config on my machine has gone bonkers... ;-) --kevan
Changes to server started messages
I noticed that the server started messages have changed. The started Web Applications are now of the following form: Web Applications: / /console /console-standard /dojo /remote-deploy Geronimo Application Server started Where they used to be: Web Applications: http://coltrane:8080/ http://coltrane:8080/console http://coltrane:8080/console-standard http://coltrane:8080/dojo http://coltrane:8080/remote-deploy Geronimo Application Server started I'm assuming that this is associated with the recent Connector changes... I preferred the old messages, but I doubt I'll lose very much sleep... Apologies if I missed discussion about this. Even more apologies if the network config on my machine has gone bonkers... ;-) --kevan
Re: Changes to server started messages
So, if we are using virtual hosts, we'll have no way of knowing which host(s) an app maps to? If we have /welcome installed on multiple virtual hosts, will we now see it listed multiple times as just /welcome ? -Donald Jeff Genender wrote: Yup... The old messages made no sense at all...because Web application != connector and therefore its not fair to determine that the web applications actually listen on http. In long discussions with David Jencks, we agreed the slapping of http in from of the URL was purely a hack and was not correct for complex cases...i.e. the applications you listed also are running on https *and* ajp. In otherwords, the web application is independent of the scheme (http) and it shouldn't know its own scheme. It *is* correct for the web application to know it's identified by the context, and thats why you see them listed. I hope this made sense. Jeff Kevan Miller wrote: I noticed that the server started messages have changed. The started Web Applications are now of the following form: Web Applications: / /console /console-standard /dojo /remote-deploy Geronimo Application Server started Where they used to be: Web Applications: http://coltrane:8080/ http://coltrane:8080/console http://coltrane:8080/console-standard http://coltrane:8080/dojo http://coltrane:8080/remote-deploy Geronimo Application Server started I'm assuming that this is associated with the recent Connector changes... I preferred the old messages, but I doubt I'll lose very much sleep... Apologies if I missed discussion about this. Even more apologies if the network config on my machine has gone bonkers... ;-) --kevan smime.p7s Description: S/MIME Cryptographic Signature
Re: Changes to server started messages
Donald Woods wrote: So, if we are using virtual hosts, we'll have no way of knowing which host(s) an app maps to? If we have /welcome installed on multiple virtual hosts, will we now see it listed multiple times as just /welcome ? Nope. The web app is deployed as just that...a web app. The web app has a single context...and that is what is reported. The URL is not fair because Tomcat can have valves that can turn on/off IP addresses/ports/etc. If we want to get into introspection of which connectors its listening on, which schemes, which ports, which virtual hosts, etc, I highly recommend we start talking about MBean exposure and JMX to do this properly and effectively. Jeff -Donald Jeff Genender wrote: Yup... The old messages made no sense at all...because Web application != connector and therefore its not fair to determine that the web applications actually listen on http. In long discussions with David Jencks, we agreed the slapping of http in from of the URL was purely a hack and was not correct for complex cases...i.e. the applications you listed also are running on https *and* ajp. In otherwords, the web application is independent of the scheme (http) and it shouldn't know its own scheme. It *is* correct for the web application to know it's identified by the context, and thats why you see them listed. I hope this made sense. Jeff Kevan Miller wrote: I noticed that the server started messages have changed. The started Web Applications are now of the following form: Web Applications: / /console /console-standard /dojo /remote-deploy Geronimo Application Server started Where they used to be: Web Applications: http://coltrane:8080/ http://coltrane:8080/console http://coltrane:8080/console-standard http://coltrane:8080/dojo http://coltrane:8080/remote-deploy Geronimo Application Server started I'm assuming that this is associated with the recent Connector changes... I preferred the old messages, but I doubt I'll lose very much sleep... Apologies if I missed discussion about this. Even more apologies if the network config on my machine has gone bonkers... ;-) --kevan
