[ http://issues.apache.org/jira/browse/DERBY-214?page=comments#action_65363 ] David Van Couvering commented on DERBY-214: -------------------------------------------
There are a lot of interesting discussions about how to call classes with main(). However, NetworkServerControl already has a well-defined set of routines that are already a documented public interface. I think that in the case of this particular situation we shouldn't change NetworkServerControl to have a new interface based on any of the proposed models. There has also been a discussion about moving argument processing out of DB2jServerImpl (now renamed NetworkServerImpl) and into NetworkServerControl. But I think that is beyond the scope of this particular JIRA item. What I am going to do for this is simply move the System.exit() from NetworkServerImpl to NetworkServerControl, and then I will open two separate items: one to relocate argument processing to NetworkServerControl, and another to adjust the other tools that don't already have a documented public interface to follow a calling model we all agree on. David > Remove System.exit() calls from the DB2jServerImpl.java > ------------------------------------------------------- > > Key: DERBY-214 > URL: http://issues.apache.org/jira/browse/DERBY-214 > Project: Derby > Type: Bug > Components: Network Server > Versions: 10.1.0.0 > Reporter: Kathey Marsden > Assignee: David Van Couvering > > The System.exit() calls needs to be removed from the > DB2jServerImpl.java as this results in the entire application > (example - Eclipse which is running the Network Server inside > it) getting shut down. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
