I think you'll need to spend some time to create a small test case. I have no idea what would cause this. depends-on would definitely not matter as Spring NEVER would create any of the Conduits. Those are only ever created within code and then passed into spring to be configured. Thus, it seems like the HTTP ConduitFactory/Transport is picking up the wrong bus somehow and we'd need to see how/where the Bus's are being created.
Dan On May 6, 2013, at 12:07 PM, geecxf <[email protected]> wrote: > Yes, I actually came to that conclusion as well as I mentioned in the two > previous replies: > > "The "depends-on" attribute would have to be in the bean with the client > code that requires the http conduit not the other way around." > > I also mentioned in my previous two messages that even if I put a > "depends-on" attribute in the right place, I get the following error: > > "Exception in thread "SpringOsgiExtenderThread-16" > org.springframework.beans.factory.BeanIsAbstractException: Error creating > bean with name 'conduit': Bean definition is abstract" > > Perhaps I'm not being clear enough. If there is any information you need to > help clarify this point please let me know. > > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problems-with-http-conduit-declared-in-OSGi-spring-configuration-tp5727009p5727294.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
