I already have a service setup to use "asadmin start-database" to start the JavaDB. This is clean and works nicely. All of the other JavaDB start mechanisms (startNetworkServer, derbyrun.jar, etc), all start and hold on to the java executable and do not start it in the background. The StartDatabaseCommand.java file of the admin-cli project creates a new java process and starts Derby with it.
I just want to augment the command with a new option that can pass the option value to the underlying java invocation that this command uses.
Further, I need to support Windows, Solaris 8 and Solaris 10, and having to maintain separate starting mechanisms for each is more complicated than simply being able to pass an option like:
asadmin --jvmoptions="-Xmx512m" start-database
[Message sent by forum member 'bbergquist' (bbergquist)]
http://forums.java.net/jive/thread.jspa?messageID=291419