[EMAIL PROTECTED] wrote:
> I understand that it is possible to run a properly configured instance of
> Geronimo using J2SE 5.0.
>
> That being said, the target audience of a Quick Start Guide/Getting Started
> document is interested in getting an instance of Geronimo up and running as
> quickly as possible. If a user downloads Geronimo and runs java -jar
> bin/server.jar and gets an exception stacktrace (or three) using J2SE 5.0,
> and then runs the same command using Java 1.4.2 and does not get a
> stacktrace (regardless of whether Geronimo is actually usable or not), then
> within that context a dependency exists on Java 1.4.2.
Geronimo 1.1 no longer prints warning messages when running under J2SE 5.0.
Here's a sample output:
[EMAIL PROTECTED]:~/dev/geronimo-1.1/jetty> java -jar bin/server.jar
Booting Geronimo Kernel (in Java 1.5.0_06)...
Starting Geronimo Application Server v1.1-SNAPSHOT
[************************] 100% 25s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
1527 0.0.0.0 Derby Connector
4201 0.0.0.0 ActiveIO Connector EJB
4242 127.0.0.1 Remote Login Listener
8009 0.0.0.0 Jetty Connector AJP13
8080 0.0.0.0 Jetty Connector HTTP
8443 0.0.0.0 Jetty Connector HTTPS
9999 0.0.0.0 JMX Remoting Connector
61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules:
EAR: geronimo/webconsole-jetty/1.1-SNAPSHOT/car
RAR: geronimo/activemq/1.1-SNAPSHOT/car
RAR: geronimo/system-database/1.1-SNAPSHOT/car
WAR: default/classloader/1147831079633/war
WAR: default/no-geronimo-plan/1147718961263/war
WAR: geronimo/remote-deploy-jetty/1.1-SNAPSHOT/car
WAR: geronimo/welcome-jetty/1.1-SNAPSHOT/car
Web Applications:
http://wildfire:8080/
http://wildfire:8080/classloader
http://wildfire:8080/console
http://wildfire:8080/console-standard
http://wildfire:8080/no-geronimo-plan
http://wildfire:8080/remote-deploy
Geronimo Application Server started
Cheers,
Erin
