There's something about the logic of that explanation that does not make sense to me (though I'll readily admit that may very well be due to my ignorance on the matter).
You say that the bundle might be picking up the wrong bus. But why would the bundle pick up the right bus on a restart? Why would it pick up the right bus if I deliberately load the configuration through the bundle context? When I step through the code, there's only one bus. What is evident from debugging the code is that the conduit is created AFTER the client calls are made, after the WebClient is created, after the init method that contains the client code is executed, and after the bean that contains that init method is instantiated. It's clearly a timing issue and probably one that is easy to reproduce by simply creating a bean with an init method that uses an http conduit declared in the same Spring configuration file. Is there any insight at all on the order of execution of these things? Are beans in a Spring configuration file created before or after the cxf configuration beans are processed? -- View this message in context: http://cxf.547215.n5.nabble.com/Problems-with-http-conduit-declared-in-OSGi-spring-configuration-tp5727009p5727299.html Sent from the cxf-user mailing list archive at Nabble.com.
