I want to do almost exactly what this poster did,
http://cxf.547215.n5.nabble.com/Dynamic-Client-Server-Side-Configuration-using-API-for-Java-First-Spring-WS-td556445.html

Except I want my WSDL Service to use SSL. I found the following project that
shows how I do it,

http://svn.apache.org/repos/asf/cxf/trunk/distribution/src/main/release/samples/wsdl_first_https/src/main/java/demo/hw_https/server/Server.java

http://svn.apache.org/repos/asf/cxf/trunk/distribution/src/main/release/samples/wsdl_first_https/src/main/resources/ServerConfig.xml

I've had some traumatic experiences in the past when dealing with the Bus.
The link below indicates that all CXF processes share things,
http://cxf.apache.org/javadoc/latest/org/apache/cxf/BusFactory.html

I definitely want each instance of my-camel to have its own Service instance
of the WSDL, each possibly uniquely configured. How do I code it so that I
can sleep at night knowing that I can have one instance of my-camel be http
and the other be https without the bus being overwritten?
getThreadDefaultBus() seems to be the solution, but...

- I'm using Servicemix, so is it safe to assume that no two bundles share
the same thread?

- If I have a camel route has two instances of my-camel, wouldn't they
theoretically be run from the same thread according to how camel works, so
wouldn't that mean they share the same thread and thus conversely the same
CXF Bus?

Someone please help me do this right... I want to sleep at night for once :
(



--
View this message in context: 
http://cxf.547215.n5.nabble.com/Custom-Camel-Component-WSDL-First-SSL-tp5734356.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to