axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ruchith Fernando <>
Subject Re: [Axis2] Phase of Inflow Security Handler
Date Thu, 25 Aug 2005 10:20:51 GMT
So are we going to include the "RequestURIBasedDispatcher" in

If that is the case we simply change the order of the dispatchers in
the "Dispatch" phase, by slightly modifying
org.apache.axis2.engine.AxisConfigurationImpl and deploy the security
IN handler in the "Dispatch" phase 'after' the

I don't think we really need two dispatch phases like that, since this
seems to be a requirement unique to the security module. what do u


On 8/25/05, Eran Chinthaka <> wrote:
> Agreed, but for HTTPand SMTP only. What about for the TCP case ? Service
> identification based on the socket information ? If so, fine.
> So lets have a phase called "DispatchPhaseOne". And the rest in
> "DispatchPhaseTwo".
> Ruchith Fernando wrote:
> >Hi All,
> >
> >When security is enabled for a certain service, the inflow security
> >handler (WSDoAllReceiver) will have to be invoked on requests to that
> >perticular service.
> >
> >Therefore we will have to deploy the WSDoAllReceiver within the
> >"Dispatch" phase after the "RequestURIBasedDispatcher".
> >
> >But the Axis2 right now enforces the "AddressingBasedDispatcher" to be
> >run ahead of all the others and this order is not configurable. But
> >IMHO we should not access the other SOAP headers before the security
> >processing is complete.
> >
> >Since RequestURIBasedDispatcher is the only possible mechanism to
> >figureout the service without accessing the other SOAP headers (e.g.
> >wsa headers) and the SOAP bosy, can we change the order of the
> >dispatchers, or can we make it configurable such that its possible to
> >change the dispatch order (to have the RequestURIBasedDispatcher
> >first),  when the security module is engaged?
> >
> >Thanks,
> >--
> >Ruchith
> >
> >
> >


View raw message