Hello

I am looking into creating a service-discovery method to register rest
endpoints in cxf running in OSGi, as an alternative to
org.apache.cxf.transport.http_jetty.osgi.HTTPJettyTransportActivator.

I realize dosgi-cxf exists, but it doesn't quite cover my use case.

But to be honest I could really use some help understanding the different
components at play here.

Can someone give me an overview over the responsibilities of the different
components at play, mainly the JettyHTTPServerEngineFactory and
JettyHTTPServerEngine.
Anything insigt you can give me into the workings and possibly caveats with
these clases would be helpful, but I also have a couple of concrete
questions:

In the documentation on this page
https://cwiki.apache.org/confluence/display/CXF20DOC/Standalone+HTTP+Transport
it seems that the TLSParameters can be registered for each "Endpoint". Is
that the JettyHTTPServerEngine engine in the code?

Is it possible to set new TLSParameters while the endpoint/engine/whichever
after services are registered to it?

How does the HTTPJettyTransportActivator clean up when it shuts down? I
don't see any cleanup in the code. Does it just garbage-collect the
endpoints if the bundle stops?

Can you point me to the classes that takes care of registering services
through blueprints? I have never really dabbled in blueprints and I am
having a hard time getting my head around it.

Thank you
-Martin

Reply via email to