On 5/31/07, David Illsley <[EMAIL PROTECTED]> wrote:
Um, can you explain what the problem actually is? We support processing headers with mustUnderstand headers, so what's the interop problem?
I can't really remember. But it happened at the checkMustUnderstand(msgContext); method in the Axis2Engine. Since Axis2 does not set mustunderstand property when the request comes from the axis2 does not give an exception and for .Net it gave. I may be my mistake or anyother problem. I suggested this as a precautionary step since if there is a problem then it can be found at the Axis2 to Axis2 testing. I'd be against setting mustUnderstand=true unless there's a strong
reason as imo it'll lead to more confusion for users. FWIW there's already a property you can set on the Options object to force the addressing handlers to mark things mustUnderstand=true David On 31/05/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > hi, > Currently, the must understand property of the addressing headers do not set > for the > required addressing headers. There is no problem with this, since there is > no compulsory requirement for that. > But MS implementation of WS* (WSF) set these attributes. > Therefore sometimes we get interop issues when processing the must > understand properties. So setting > must understand property true within the Axis2 would resolve these > incompatibility issues easily. > > So shall we switch on the must understand property for all the required > addressing headers if there is no > reason for not to do so. > I think it is better to do the same thing for rampart and sandesha too. > > if we decide to do so can someone go ahead and do the changes since I am not > much familiar with the addressing. > > thanks, > Amila. > > > -- > Amila Suriarachchi, > WSO2 Inc. -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Amila Suriarachchi, WSO2 Inc.
