Il 23.09.2014 15.16, John I. Moore, Jr. ha scritto:
One minor thought to add to this discussion:
If the main reason for adding Derby as a service is so it will start running
whenever
Windows starts, Windows Task Scheduler can be used for this purpose, and I
found it much
easier to use that Apache commons Daemon.
No, the main reason is to start and stop derby when I need. The big
advantage of Apache commons Daemon is that enables you to control the
service (including startup parameters) by a single wonitor window that
stay silently iconized in the window toolbar. Not that I'm aware of,
just two different ways to achive the same thing. Feel free to add a
section on how to accomplish the task with the Apache Commons Daemon.
Regards,
