Absolutely - hopefully I just misconfigured something. Also attached is the axis2.xml.
In the version attached the OutFlow of the module is associated with the built-in Dispatch phase and the InFlow is associated with the user-defined asiFactoryPhase. Neither seems to be invoked. BTW, I also tried specifying the module at the service scope in services.xml with the same result. Thanks, Mike > On Wed, 2006-12-13 at 09:40 +0530, Deepal Jayasinghe wrote: > > Hi Mike Morris ; > > > > Any possibility of attaching module.mar file . > > > > Thanks > > Deepal > > > > >I have just started taking a look at porting an ws implementation based > > >on Axis 1.4 to Axis2. I am deploying my implementation in the axis.war > > >file, adding my service (.aar) to the WEB-INF/services directory. This > > >works fine - I can access my service using the wsdl2java generated > > >stubs. > > > > > >I then packaged and added the module (.mar) to the WEB-INF/modules > > >directory and updated the axis2.xml file to declare the module in global > > >scope. When I access the service, the module is loaded and the handler > > >initialized but the invoke() method is never called during the phase > > >execution chain. I stepped through the AxisEngine code and it does not > > >appear that the phase i am specifying in the axis2.xml file is ever > > >loaded, though I do see the built-in phases (Transport, PreDispatch, > > >etc). > > > > > >Any help? > > > > > >Thanks, > > >Mike > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
