I think this is similar to what Freeman and I spent a couple hours debugging
yesterday. I couldn't reproduce it at first as it didn't seem to appear when
using Equinox (which is what I normally use). It only appeared with Felix.
I was finally able to reproduce it with Felix and put a fix in place
yesterday. Any chance you could try with the latest snapshots of 2.4.4-
SNAPSHOT of 2.5.0-SNAPSHOT? Also, could you try flipping to Equinox and
seeing if the problem goes away?
Dan
On Friday, October 14, 2011 7:48:50 AM bst wrote:
> 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.
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
Talend - http://www.talend.com
