On 4/18/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Corey;
In axis2 you have two types of phases called global and operation
specific. Security phase is said to be a global phase , what that mean
is when you add a handler into such a phase those handler will run on
each web service invocation irrespective of the service.
So in ur case even though you have engage your module into ur service ,
it is adding a handler into global phase. That is the reason behind
running ur handler even when you invoke version service .
But if you add ur handler into operation phase (phases listed after
Dispatch phase) that will not happen.
Corey Baswell wrote:
> Greetings,
> I have created a module who's module xml file looks like the following:
>
> /<module name="securitymodule">/
> / <Description>Security Module</Description>
> <inflow>
> <handler name="InSecurityHandler" class="classnamexx>
> <order phase="Security"/>
> </handler>
> </inflow>
> </module>/
>
>
> Then within my service archive I reference this module from
> services.xml like this:
>
> /<service>
> <description>Service desc</description>
> <module ref="securitymodule"/>
> <operation name="UpdateLevels">
> <messageReceiver
> class="gov.nasa.service.axis2.receivers.InOutJBIReceiver" />/
> / </operation>/
> /</service>/
> //
> This works correctly meaning that when I call my service the
> /InSecurityHandler /is engaged in the Security phase. However when I
> use the /getVersion/ default Axis2 service, the InSecurityHandler is
> invoked there as well. My question is should this be happening since
> the securitymodule is not referenced the /getVersion/ service archive
> file (services.xml)? And if it is (supposed to be happening), can I
> prevent this somehow?
>
> Thanks for any help,
>
> Corey
--
Thanks,
Deepal
................................................................
~Future is Open~
