Re: hrefs where SOAP-ENC:root is not supplied - interop issue wit h .N

[Bill Greenseth <Bi...@Snapnames.com>]

We're trying out a possible fix for this problem which is to change line 137
of RPCProvider.java as below.

old - if (bodyEl.isRoot() && operation != null) {
new - if (bodyEl.isRoot() && operation != null && bodyEl.getID() == null)

Bill

> We have run into this same issue and I agree with Jason that it 
> would be best if Axis handled body elements that are not root elements 
> but have the soapenc:root="0" tag omitted. Is there consensus 
> in the Axis community on this? If so, I or one of my colleagues
> can suggest an Axis code change, but I'd like to get a better idea 
> of what people think about this general issue first.

> Blake

> -----Original Message-----
> From:         Blumenkrantz, Jason  
> Sent: Wednesday, May 01, 2002 10:24 AM
> To:   Axis-User (E-mail)
> Subject:      RE: Deserialization error upgrading from Beta 1 => Beta 2
>
> Upon looking into it further, it looks like Axis Beta 2 is unable to
handle
> HREFs where SOAP-ENC:root is not supplied. From the Axis client,
> SOAP-ENC:root is set to "0" on the attached bean. However, .NET is not
> including SOAP-ENC:root attributes. So the method call in the first body
> element is succeeding, but then RPCProvider is attempting to execute the
> attached bean as a method call, since bodyEl.isRoot() returns true for the
> attached bean with no SOAP-ENC:root. Since the root attribute is not
> required by the SOAP spec, shouldn't Axis be better handling those body
> elements that are not root elements but have the tag omitted?
> -Jason
>