I believe I have found the problem. Glen's suggestion of using a debugger to figure out the problem turned out to be a very good one. I put breakpoints in the following places:
HTTPConduit constructor SpringBus constructor SpringBus setApplicationContext() method Start of my client code End of my client code Those breakpoints were enough to reveal the problem. The problem is that the CXF bus bean I want my client to use gets created AFTER Spring creates the class with the client code that I want to use that bus. Injecting the bus as a property works because it creates a dependency which forces Spring to create the bean BEFORE creating the class with the client code. Thus the problem seems to be one of ordering the Spring instantiation of the CXF bean and whatever code would use that bean. Lesson learned. One straightforward solution to this problem is to add a "depends-on" attribute to any potential bean that might use the cxf bus bean. That guarantees the bean is available before you try to use it. Thanks, D -- View this message in context: http://cxf.547215.n5.nabble.com/Code-only-STSClient-tp5724575p5724943.html Sent from the cxf-user mailing list archive at Nabble.com.
