Hi Freeman,
well I did some debugging lately and found out what really caused my
problem. Actually it is the
org.apache.cxf.transport.servlet.CXFNonSpringServlet who gets
spring-initiated with the "empty" DestinationRegistry which doesn't have
reference to any TransportFactory respectively no transportId gets
registered:
<bean id="osgiServlet"
class="org.apache.cxf.transport.servlet.CXFNonSpringServlet">
<constructor-arg ref="destinationRegistry"/>
</bean>
My workaround which did the trick is to use default-constructor:
<bean id="osgiServlet"
class="org.apache.cxf.transport.servlet.CXFNonSpringServlet" />
... and let the CXFNonSpringServlet create the DestinationFactory itself
with reference to the HTTPTransportFactory:
if (destinationRegistry == null) {
// no destination registry associated -> create the new one
this.destinationRegistry =
getDestinationRegistryFromBus(this.bus);
}
Cheers,
Boris
--
View this message in context:
http://cxf.547215.n5.nabble.com/osgi-problem-since-2-4-0-tp4786635p4902843.html
Sent from the cxf-user mailing list archive at Nabble.com.
