----- Original Message ----
From: John H. Embretsen (JIRA) <[email protected]>
To: [email protected]
Sent: Wednesday, May 24, 2006 7:49:30 AM
Subject: [jira] Commented: (DERBY-1293) Derby Server and Administration Guide -
derby.drda.startNetworkServer
[
http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12413131 ]
John H. Embretsen commented on DERBY-1293:
------------------------------------------
Adding the most recent proposal from the derby-dev list
(http://www.nabble.com/-jira-+Created%3A+%28DERBY-1293%29+Derby+Server+and+Administration+Guide+-+derby.drda.startNetworkServer-t1564099.html#a4247615)
to this Jira-issue for review:
== START ==
Use the derby.drda.startNetworkServer property to simplify embedding the
Network Server in your Java application.
When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start when you start Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.
NOTE:
Please be aware that if the Network Server is started using this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system), whichever
comes first.
== END ==
Hi John,
This looks good to me. Just from a consistency standpoint, having written
almost all of the other documentation, there are a couple cosmetic changes I'd
recommend to keep this similar to the rest of the writing:
When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start with Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.
NOTE:
If you start the Network Server with this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system, whichever
comes first).
