Re: [Axis2] Dispatch order

2007-12-20 Thread Amila Suriarachchi
Sometimes we may not need this change and have to move the security phase after dispatching. Please see the possible two security attacks I have mentioned here. https://issues.apache.org/jira/browse/RAMPART-127 Thanks, Amila. On Dec 20, 2007 11:24 AM, Amila Suriarachchi [EMAIL PROTECTED]

Re: [Axis2] Dispatch order

2007-12-20 Thread Nandana Mihindukulasooriya
Hi, Sometimes we may not need this change and have to move the security phase after dispatching. Please see the possible two security attacks I have mentioned here. I think we have to have the operation dispatched before the security phase in all cases. Otherwise there will be no way of

Re: [Axis2] Dispatch order

2007-12-19 Thread Amila Suriarachchi
On Dec 19, 2007 8:32 PM, David Illsley [EMAIL PROTECTED] wrote: So what's the plan? Where are you going to move the code to? yes. What I thought was to get this code to a separate dispatcher and set this dispatcher as the first dispatcher in the Transport phase. Amila David On Dec 19,

Re: [Axis2] Dispatch order

2007-12-19 Thread David Illsley
Um, presumably it should go after the RequestURIBasedDispatcher so you don't have to redo the service dispatch? David On Dec 19, 2007 3:27 PM, Amila Suriarachchi [EMAIL PROTECTED] wrote: On Dec 19, 2007 8:32 PM, David Illsley [EMAIL PROTECTED] wrote: So what's the plan? Where are you going

Re: [Axis2] Dispatch order

2007-12-19 Thread Sanjiva Weerawarana
The issue here is whether SUPPORT_SINGLE_OP takes priority or the sequence of deployers do. That is, right now it appears that SSO is tested at the end of the dispatch phase .. which just makes sure that if that property has been set it overrides everything else. Service dispatch also happens

Re: [Axis2] Dispatch order

2007-12-19 Thread Amila Suriarachchi
On Dec 19, 2007 9:40 PM, David Illsley [EMAIL PROTECTED] wrote: Um, presumably it should go after the RequestURIBasedDispatcher so you don't have to redo the service dispatch? yes David On Dec 19, 2007 3:27 PM, Amila Suriarachchi [EMAIL PROTECTED] wrote: On Dec 19, 2007 8:32 PM,

Re: [Axis2] Dispatch order

2007-12-19 Thread Amila Suriarachchi
On Dec 20, 2007 8:06 AM, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: The issue here is whether SUPPORT_SINGLE_OP takes priority or the sequence of deployers do. No. the matter is whether this dispatch should run before the security phase or not. just think the senario where this operation has

[Axis2] Dispatch order

2007-12-18 Thread Amila Suriarachchi
hi all, 1. Here is a code segment found in the org.apache.axis2.engine.DispatchPhase checkPostConditions method. if (operation == null JavaUtils.isTrue(service.getParameterValue( AxisService.SUPPORT_SINGLE_OP))) { Iterator ops = service.getOperations();

Re: [Axis2] Dispatch order

2007-12-18 Thread Amila Suriarachchi
On Dec 19, 2007 10:00 AM, Amila Suriarachchi [EMAIL PROTECTED] wrote: hi all, 1. Here is a code segment found in the org.apache.axis2.engine.DispatchPhase checkPostConditions method. if (operation == null JavaUtils.isTrue(service.getParameterValue (

[Axis2] Dispatch order

2006-01-30 Thread Ruchith Fernando
Hi All, Axis2 default dispatching order is now changed to the following : RequestURIBasedDispatcher SOAPActionBasedDispatcher AddressingBasedDispatcher SOAPMessageBodyBasedDispatcher The motivation behind this change is to insert the security-IN-flow handler after the SOAPActionBasedDispatcher.

Re: [Axis2] Dispatch order

2006-01-30 Thread Davanum Srinivas
+1 from me. On 1/30/06, Ruchith Fernando [EMAIL PROTECTED] wrote: Hi All, Axis2 default dispatching order is now changed to the following : RequestURIBasedDispatcher SOAPActionBasedDispatcher AddressingBasedDispatcher SOAPMessageBodyBasedDispatcher The motivation behind this change is