We have a requirement that says we have to support hosting web services on multiple ports. Perhaps there's another way to accomplish that other than using CXF DOSGi with absolute addresses?
From: "Sergey Beryozkin-5 [via CXF]" <ml-node+s547215n572141...@n5.nabble.com<mailto:ml-node+s547215n572141...@n5.nabble.com>> Date: Thursday, January 10, 2013 9:29 AM To: GE GE <am...@ge.com<mailto:am...@ge.com>> Subject: Re: SSL with DOSGi On 10/01/13 17:27, Sergey Beryozkin wrote: > Hi > On 10/01/13 17:07, geecxf wrote: >> Hi Sergey, >> >> Thanks for the prompt response. The more I read through the CXF DOSGi >> code the more your revelation makes sense. It seems like the only >> configuration file that affects cxf.dosgi.dsw is the cxf-dsw.cfg >> through Felix FileInstall. However, I can't see any properties that >> affects the default bus when using an absolute addresses. >> >> So it looks like I would have to affect the BusFactory class which >> seems to read some bus configuration from external sources. Which begs >> the question: >> >> Could I alter the default bus configuration to support https though a >> META-INF/cxf/cxf.xml file in the manner described here >> http://cxf.apache.org/docs/configuration.html? Then build a new >> cxf-dosgi-ri-singlebundle-distribution that by default will create >> HTTPS endpoints instead of HTTP when specifying absolute addresses? >> Would this approach work? >> > > I wonder if that will work even if you declare cxf:bus in your > application context, alongside http-jetty configuration and DOSGi will > pick up it, but I'm not sure; you may need to experiment, but I doubt > that rebuilding a single bundle distro would be the right approach, > ideally, there was some way to get DOSGi picking up the SSL-aware > default bus >> My follow-up question is that if the approach described above works, >> it is obviously a hack. Was there a vision for SSL support when using >> absolute addresses? What would such a feature look like? Or is any >> solution OK as long as it does not violate the DOSGi specification? > > As far as I recall, no support for HTTPS was on the map at a time, > > By the way, why using OSGI HTTP Service does meet the requirements ? > does *not* meet ? > Cheers, Sergey > >> >> Thanks, >> >> D >> >> From: "Sergey Beryozkin-5 [via >> CXF]"<[hidden >> email]</user/SendEmail.jtp?type=node&node=5721416&i=0><mailto:[hidden >> email]</user/SendEmail.jtp?type=node&node=5721416&i=1>>> >> >> Date: Thursday, January 10, 2013 8:31 AM >> To: GE GE<[hidden >> email]</user/SendEmail.jtp?type=node&node=5721416&i=2><mailto:[hidden >> email]</user/SendEmail.jtp?type=node&node=5721416&i=3>>> >> Subject: Re: SSL with DOSGi >> >> Or rather, no one has looked yet into trying to get the bus aware of >> such configuration found and selected somehow when absolute >> org.apache.cxf.rs/ws.addresses are used :-) >> >> >> >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/SSL-with-DOSGi-tp5721344p5721413.html >> Sent from the cxf-user mailing list archive at Nabble.com. > ________________________________ If you reply to this email, your message will be added to the discussion below: http://cxf.547215.n5.nabble.com/SSL-with-DOSGi-tp5721344p5721416.html To unsubscribe from SSL with DOSGi, click here<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5721344&code=YW1pcmlAZ2UuY29tfDU3MjEzNDR8LTE3ODgxMjU0NzM=>. NAML<http://cxf.547215.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://cxf.547215.n5.nabble.com/SSL-with-DOSGi-tp5721344p5721418.html Sent from the cxf-user mailing list archive at Nabble.com.
