Hi Christian, An option to configure SSL contexts programmatically seems to be discussable DOSGi extension. What do you think?
Regards, Andrei > -----Original Message----- > From: Martin Nielsen [mailto:[email protected]] > Sent: Freitag, 23. Juni 2017 09:46 > To: [email protected] > Subject: Re: Help understanding the OSGi based CXF rest service registration > > The main reason i started this project is that i could not i find a project > which > allowed me to control the SSL context of hosted services programatically. I > needed a way to configure Key -and Trust managers programmatically. Then > only solutions i could find allowed me to point to keystores somewhere on the > filesystem. What i need is to inject my own trust and keystore > implementations. > > So that is the reason I decided to attempt my own version. I actually started > out > by trying to figure out how to introduce that functionality into cxf-dosgi, > but > there is no access to to the actual cxf engine. So it didn't seem to be in > tune > with the overall design of the project. > > > > On Fri, Jun 23, 2017 at 7:14 AM, Christian Schneider < chris@die- > schneider.net> wrote: > > > Before creating something completely new I recommend you explain what > > your requirements are. Maybe there is an existing project you can help > > improve instead of creating another way to export JAX-RS services. > > > > You mention that CXF-DOSGi does not cover your case. What are you > missing? > > > > There is also https://github.com/apache/aries-jax-rs-whiteboard which > > covers a similar case as DOSGi in a slighty different way. > > > > Christian > > > > 2017-06-06 12:03 GMT+02:00 Martin Nielsen <[email protected]>: > > > > > 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 > > > > > > > > > > > -- > > -- > > Christian Schneider > > http://www.liquid-reality.de > > > <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7 > > e 46&URL=http%3a%2f%2fwww.liquid-reality.de> > > > > Open Source Architect > > http://www.talend.com > > > <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7 > > e > > 46&URL=http%3a%2f%2fwww.talend.com> > >
