Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
  b=YceOlK6carZ2wrGgNvmFZjwkmqq0x9os8j7z4SJccRUq4OXmy+7zHkOGxaLcjz+vaScn7UueZStnZB/iBvIr/5lNbhTGnJwVS/7tyBvL99A6DIB6hBD1yGt/neQsahOb3Fpwqh4YZqw/cCwsJ1naCJVQwOKr3s9oF+OTnYgAceM=
  ;
Mime-Version: 1.0 (Apple Message framework v622)
In-Reply-To: <438F8D38.9090805@gmail.com>
References: <438F8D38.9090805@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <e4aa8e9fd38b47eb6df0b194b9092854@yahoo.com>
Content-Transfer-Encoding: 7bit
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: Should we change the default startup progress format for 1.0?
Date: Thu, 1 Dec 2005 15:59:54 -0800
To: dev@geronimo.apache.org

I like this much better

david jencks

On Dec 1, 2005, at 3:54 PM, John Sisson wrote:

> A few people have suggested we change the default startup format to 
> one that doesn't use line feeds to update the progress of a 
> configuration that is being loaded.
>
> I like the existing startup format as it looks fancy and doesn't 
> produce as many lines of output than the longer format (see example 
> below), but it isn't very usable when error messages are issued as the 
> display of the error can end up being garbled due to the thread that 
> updates the configuration status line (using line feeds) every 500ms.  
> This could become a support issue.
>
> Now is the time to decide, as it will be harder to change our minds 
> later after 1.0.
>
> I am proposing that the existing default progress output be used when 
> the -s or --short option is specified.  This will impact existing 
> documentation.
>
> Here is an example of the output in the proposed long format:
>
> Booting Geronimo Kernel (in Java 1.4.2_08)...
> Started configuration  1/15   0s org/apache/geronimo/RMINaming
> Started configuration  2/15   2s org/apache/geronimo/RuntimeDeployer
> Started configuration  3/15   0s org/apache/geronimo/Jetty
> Started configuration  4/15   2s org/apache/geronimo/Tomcat
> Started configuration  5/15   0s org/apache/geronimo/Server
> Started configuration  6/15   0s org/apache/geronimo/Security
> Started configuration  7/15  10s org/apache/geronimo/ActiveMQServer
> Started configuration  8/15   0s org/apache/geronimo/SystemJMS
> Started configuration  9/15   0s org/apache/geronimo/SystemDatabase
> Started configuration 10/15   2s org/apache/geronimo/Directory
> Started configuration 11/15   0s 
> org/apache/geronimo/JettyRuntimeDeployer
> Started configuration 12/15   0s 
> org/apache/geronimo/TomcatRuntimeDeployer
> Started configuration 13/15   1s 
> org/apache/geronimo/applications/Welcome/Jetty
> Started configuration 14/15   1s org/apache/geronimo/Console/Jetty
> Started configuration 15/15   0s org/apache/geronimo/HotDeployer
> Startup completed in 21 seconds
>  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 0.0.0.0 Remote Login Listener
>    8019 0.0.0.0 Tomcat Connector AJP
>    8080 0.0.0.0 Jetty Connector HTTP
>    8090 0.0.0.0 Tomcat Connector HTTP
>    8443 0.0.0.0 Jetty Connector HTTPS
>    8453 0.0.0.0 Tomcat Connector HTTPS
>   61616 0.0.0.0 ActiveMQ Message Broker Connector
>
>  Started Application Modules:
>    EAR: org/apache/geronimo/Console/Jetty
>    WAR: org/apache/geronimo/applications/Welcome/Jetty
>
>  Web Applications:
>    http://JSLAP:8080/
>    http://JSLAP:8080/console
>    http://JSLAP:8080/console-standard
>
> Geronimo Application Server started
>
> John
>