On Thu, Apr 2, 2009 at 12:01 PM, Azazel Se <[email protected]> wrote: > Thanks Sagara. > I actually tried that one first but I didn't know which of the suppliers > was the correct one so I tried both. In my mail I pasted the exception > from SpringAppContextAwareObjectSupplier twice by accident. When > using SpringServletContextObjectSupplier I got a "No bean named 'MyServ' > exception, but when I added: > > <bean id="MyServ" > class="xyz.MyServ"> > </bean> > > to the context.xml file the error went away. So now it deploys and runs > without errors, I also got the test string back in my ws-client. But later > when I tried using the context I get > from ApplicationContextHolder.getContext() I found that it has value null??? > Anyone know why? >
"ApplicationContextHolder.getContext()" isn't needed when using SpringServletContextObjectSupplier. If spring and axis2 are working together, you are done. You have to configure Spring to use ApplicationContextHolder, otherwise it will return null values. - R
