Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <42707488.4060107@sbcglobal.net>
Date: Wed, 27 Apr 2005 22:28:40 -0700
From: Kathey Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [jira] Commented: (DERBY-214) Remove System.exit() calls from
 the DB2jServerImpl.java
References: <124244851.1114624173884.JavaMail.jira@ajax.apache.org>
In-Reply-To: <124244851.1114624173884.JavaMail.jira@ajax.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

David Van Couvering (JIRA) wrote:

>
>  Is it OK for NetworkServerControl to call System.exit, or does that need to throw an exception as well?
>
>The technique I usually do for a utility that I want callable by another class as well as executable from the command line is for the main() routine to delegate to another public method which throws exceptions and doesn't call System.exit().  Then the main() routine catches any exceptions and calls System.exit(1) if there is an exception or System.exit(0) if there isn't one.  Then classes call the other public method and main() is only used from the command-line.
>  
>

The execute() method which is the one with the System.exit is only
called by NetworkServerControl.main()  so I guess it is the exit even
from main that is causing a problem with eclipse.  For the exit(0),  I
guess we could just return.  For the exit(1) case I am not entirely sure
what  is appropriate.    Maybe  main should just throw the exception
then we get an error exit but the calling program won't exit completely.

Rajesh filed the original case when he had a problem with eclipse
exiting completely when he tried to use the main method from within
eclipse.  Rajesh could you confirm that  that is the case?

Kathey