[
https://issues.apache.org/activemq/browse/SM-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45672#action_45672
]
Guillaume Nodet commented on SM-1576:
-------------------------------------
Instead of renaming start / stop methods, which usually do already what we
want, we need to leverage the activate / deactivate methods, changing those so
that they don't automatically call start / stop.
In addition, for servicemix-http, the jetty contexts have a shutdown state
which can be used, but it seems to bypass any processing thus the client won't
receive anything. It may be better to return a 503 error instead.
> Change endpoints lifecycle to use init / start / stop / shutdown
> ----------------------------------------------------------------
>
> Key: SM-1576
> URL: https://issues.apache.org/activemq/browse/SM-1576
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-common
> Reporter: Guillaume Nodet
> Fix For: 3.3
>
>
> Change servicemix-common in the following way:
> * refactor the existing start / stop method into init / shutdown (along
> with the doStart and doStop methods)
> * add new start / stop methods with empty implementation in the Endpoint
> class
> * use these new init / start / stop / shutdown lifecycle in the service
> unit
> * implement start / stop for the polling endpoints
> * implement start / stop for the jms consumer endpoint (it should start /
> stop the listener container)
> * implement start / stop for the http consumer (a stopped endpoint should
> return an 503 Service Unavailable http status code)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
