[
https://issues.apache.org/jira/browse/DIRSERVER-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1346:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> Use ServiceLifecycleListener to avoid having System.out messages for service
> start/stop events.
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1346
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1346
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.4
> Reporter: Alex Karasulu
> Priority: Trivial
> Fix For: 2.0.0-RC1
>
> Attachments: DIRSERVER-1346.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
