Thank you Charles and Willem for your responses!
I try to collect the information I received from you:
- I do not have to change my cxfEndpoint configuration. It can/should looks
like the following:
<camel-cxf:cxfEndpoint id="wsService"
address="services/OrderEntryService"
serviceClass="com.company.product.OrderEntryService"/>
- In my Spring configuration, the cxf resource imports should looks like the
following:
<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-http.xml" />
<import resource="classpath:META-INF/cxf/osgi/cxf-extension-osgi.xml" />
This means I have to remove the import:
<import resource="classpath:META-INF/cxf/cxf-extension-http-jetty.xml" />
And add the imports:
<import resource="classpath:META-INF/cxf/cxf-extension-http.xml" />
<import resource="classpath:META-INF/cxf/osgi/cxf-extension-osgi.xml" />
I still have to questions:
- The import of the resource "META-INF/cxf/osgi/cxf-extension-osgi.xml"
introduce a dependency to OSGI which we normaly configure in a separate
Spring configuration (bundle-context-OSGI.xml). Should we put this import
into bundle-context-OSGI.xml and in our unit tests, which didn't load this
Spring configuration, we should import another or no additional resource?
- If I want test this route in a normal unit test (no OSGI environment), do
I have to start e.g. Jetty be myself and CXF will detect this and use the
Jetty? Is there any code you can share with me?
- Something else I have to have in mind?
Thanks in advance,
Christian
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3409357.html
Sent from the Camel - Users mailing list archive at Nabble.com.
