+1 on Adding a new phase and moving addressing BasedDistpacher before the Security. In this way we can support operational level security polices. I think it is very difficult for a new person to debug and find this problem (handler chain order) if we have shif it in wrong way. Since one of the objectives of Axis2 1.3 to provide a Sandesha and rampart compatible Axis2 release it would be nice to have this for Axis2 1.3.
Thanks Amila. On 7/24/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
I will introduce a new phase called "Addressing " and go forward , let's revert that if we found and issue. Thanks Deepal Sanjiva Weerawarana wrote: > +1 ... I think we need to ship an Axis2 that can compose nicely and > easily with Rampart and Sandesha to make secure+RM work correctly for > HTTP and SMTP (basically for all transports we support). > > Sanjiva. > > Deepal Jayasinghe wrote: >> Hi Dims, >> >> No the issues is client side when someone tries to use RM+ Security then >> he has to go and change axis2.xml. Other thing is for security to work >> correctly it is required to have addressing based dispatcher before >> security handlers. And using a security is common case so I think >> default axis2.xml should support that. >> >> Thanks >> Deepal >>> Deepal, >>> >>> IMHO, This can be documented and fixed post 1.3 I can see folks who >>> are working on an advanced scenario comfortable with a custom >>> axis2.xml. >>> >>> thanks, >>> dims >>> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Amila Suriarachchi, WSO2 Inc.
