This one time, at band camp, Dain Sundstrom said:
DS>On Sep 13, 2004, at 9:59 AM, Jeremy Boynes wrote:
DS>
DS>> System property is a really bad idea - for example, if you are running
DS>> multiple connectors which one does it apply to? Or are you suggesting
DS>> a whole hierarchy of properties?
DS>
DS>It wouldn't be something you would use in production, just during
DS>setup. Right now, jetty uses jetty.port, and if this is set it uses it
DS>for the default http connector. We could use this for the current
DS>single default web connector we install.
DS>
DS>If you are concerned, we could add a property "look for a system
DS>property" to the connector and only turn it on in our default
DS>connector. Anyway, it would be just one property, for one default http
DS>connector, just for setup when our default port is blocked.
DS>
DS>> You also have control via JMX remoting with its own set of connectors
DS>> - for example, you could use RMI for this with the current default
DS>> config.
DS>
DS>What if the RMI port is blocked? You need some way to bootstrap the
DS>system so you can connect a console.
Again, this was my point. If there is no manner in which to bring
up Geronimo to get to the JMX remoting, the user is out of luck.
Is a single system property going to reek that much havoc?
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL
PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html
