[
https://issues.apache.org/jira/browse/LANG-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
offbynull updated LANG-878:
---------------------------
Description:
It would be nice if commons lang had a Service class for threading -- similar
to the one provided by Guava, but without Guava's poorly designed API and
excess baggage. This would essentially be a thread with an initialization
method and a shutdown method (along with the actual run method). The thread
creating the service would block until the initialization finishes
successfully, and the service would call shutdown when it finishes (or if it
gets interrupted). You would be able to query the state of the Service at any
time.
It would live in the concurrent package.
was:
It would be nice if commons lang had a Service class for threading -- similar
to the one provided by Guava, but without Guava's poorly designed API and
excess baggage. This would essentially be a thread with an initialization
method and a shutdown method (along with the actual run method). The thread
creating the service would block until the initialization finishes
successfully, and the service would call shutdown when it was finished (or if
it was interrupted). You would be able to query the state of the Service at any
time.
It would live in the concurrent package.
> Create a service implementation
> -------------------------------
>
> Key: LANG-878
> URL: https://issues.apache.org/jira/browse/LANG-878
> Project: Commons Lang
> Issue Type: Wish
> Reporter: offbynull
> Priority: Minor
>
> It would be nice if commons lang had a Service class for threading -- similar
> to the one provided by Guava, but without Guava's poorly designed API and
> excess baggage. This would essentially be a thread with an initialization
> method and a shutdown method (along with the actual run method). The thread
> creating the service would block until the initialization finishes
> successfully, and the service would call shutdown when it finishes (or if it
> gets interrupted). You would be able to query the state of the Service at any
> time.
> It would live in the concurrent package.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
