[DIRSERVER-1346] Use ServiceLifecycleListener to avoid having System.out messages for service start/stop events.

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 1.5.4
• Fix Version/s: 2.0.0-M13
• Assignee: Unassigned
• Reporter: Alex Karasulu
• Created: 09/Apr/09 16:21
• Updated: 20/Jun/13 10:12
• Resolved: 17/May/13 07:54

Description

In the following commit a number of System.out lines were added to various ApacheDS services:

http://svn.apache.org/viewvc?view=rev&revision=696371

I understand that this was done to facilitate Studio's server log which displays the starting and stopping of various services. The problem with this is that is generates a lot of output clutter during test that are run when building the project. Sometimes one feels as though the test failed since they're used to the old format. I don't think this information is that worth while to have on the command line but it it does make sense in Studio's log view.

Fixing this is simple. We can create a basic ServiceListener interface which contains the start() and stop() methods. The services can then have some code to notify registered listeners. Then an implementation can be created to just print out these status messages to the console when the services are being used in Studio.