I have an existing (headless) application that initializes Spring context via a Startup Servlet using FileSystemXmlApplicationContext (spring config files are deployed outside the ear file/not on classpath).
We are now exposing our java api as a web service.
I am using annotations and dynamic wsdl to start and have tried a few things
1) I tried adding the sws config to existing set of spring config files and loading with my StartupServlet
But it seems that the config is required in WEB-INF/spring-ws-servlet.xml
2) I created spring-ws-servlet.xml and moved sws config there
Now my wsdl is generated but Spring can't see any of the beans in the context created earlier...so the service bean auto-wired into the endpoint is missing...I suspect that this is a new spring container/spring context being created.Code:<sws:annotation-driven /> <sws:dynamic-wsdl ... </sws:dynamic-wsdl>
So how do I bridge these two contexts together?
-we prefer, if possible, to have all our resource/config files externalized from the ear file. (legacy IT shop reasons).
Thanks for any help.


Reply With Quote