If I understand you correctly, you just need to get a hold of your beans anytime, anywhere. If you are doing Spring inside the AAR, you already defined 'bean id="applicationContext"' . If not, you can still make use of it. At the web-app level , axis2 uses that bean to get its spring beans to make a Service out of it. This all takes advantage of the Spring's ApplicationContextAware interface. Its perfectly fine for you to use the static method that Axis2's internals use also:
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/spring/src/org/apache/axis2/extensions/spring/receivers/SpringAppContextAwareObjectSupplier.java?view=markup Here's some javadoc: http://ws.apache.org/axis2/1_2/api/org/apache/axis2/extensions/spring/receivers/ApplicationContextHolder.html http://www.springframework.org/docs/api/org/springframework/beans/factory/BeanFactory.html#getBean(java.lang.String) HTH, Robert On 8/10/07, John Pfeifer <[EMAIL PROTECTED]> wrote: > > > > > I currently have my web services running with axis2 (1.1) and spring running > inside the aar. Recently I have discovered a need for servlets and/or web > pages to get access to the objects that are in the spring context. If I > move spring to the WEB-INF/lib, can I do this? The Axis2-Spring integration > docs don't go into much detail here. I guess what I am wondering is whether > or not the aar files are available at the time the Spring > ContextLoaderListener starts up. If so, this should work. > > Thanks, > > John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
