Hi,
Scenario: standalone CXF service registers endpoint using following code:
...
Object implementor = new GreeterSoapMessageProvider();
String address = "http://localhost:9000/SoapContext/SoapPort1";;
Endpoint ep = Endpoint.publish(address, implementor);
...
The service starts Jetty instance and uses JettyHTTPDestination - that's fine.
After some activities, code closes endpoint using ep.stop().
The user expectation is that JettyEngine will be closed and after exiting from
main() application will be finished.
Currently Endpoint.stop() unregisters listeners and message observers, removes
endpoint path from the destination registry, but leaves JettyEngine running. As
result some qtp threads continue to run and service application hangs after
exiting from main() method.
Are there any special reason for such behaviour? Does it makes sense to
shutdown JettyEngine when no active endpoints are there at least for standalone
deployment?
Regards,
Andrei.
