On Tue, Dec 16, 2008 at 1:08 PM, Paul French <paul.fre...@kirona.com> wrote: > Thanks for the reply. > > Its not what I am after though. We have AXIS2 as part of our web > application. We have web services which are defined as beans in the Spring > application context loaded as part of the web application. > > We also want our modules defined as beans from the same application context. > For example our logging module requires a datasource. This datasource is > already defined in Spring for the web application. I suppose I am trying to > avoid having to setup things twice in 2 different places. >
Well that's why I mentioned the Classloader reference issue, in case you needed it, and you do. IIRC both Modules and AAR's have their own classloader. Axis2Service is used to supply the Classloader reference in the AAR case. I'm not sure how to get the equivalent in Module.init() as I see no examples in the source, or even if you did it'd work correctly with the Classloader stuff in AbstractMessageReceiver. Maybe someone like Deepal can comment further. - R
