This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

But however, at runtime I found the dependency injection never happened. After looking into Spring's code, I guess the problem might be that Spring probably requires that my WS servlet and ContextLoaderListener should be able to get access to exactly the same thread context class loader (i.e. the classloader for the webapp), but when weblogic processes my servlet, it temporarily sets the thread context class loader to a dedicated JAXWS class loader which inherits from the regular webapp class loader, and this causes that my servlet can't share the spring application context of the webapp, so that the DI gets ignored.

If I'm not doing anything wrong, I just wonder if there's any solution on the spring side?

I am trying to do the same thing and it doesnt seem to work. Has anyone tried using the SpringBeanAutowiringSupport on endpoint and got the injection working? I have spent a lot of time on this and am going nowhere. I am using weblogic 10.3 onJava 6

DEBUG: org.springframework.web.context.support.SpringBeanAutowiringSupport - Current WebApplicationContext is not available for processing of HelloWorldEndpoint: Make sure this class gets constructed in a Spring web application. Proceeding without injection.