type mapping: soapenc and xsd

[Mati David <ma...@bitband.com>]

Hi,

 

We've just upgraded the axis jar in our project to axis 1.3 from axis
1.1.

After this upgrade the wsdl file (which is automatically generated) has
different types mapping -

It now somehow uses soapenc namespace instead of xsd (so for example
when ever I used to see xsd:string I now see soapenc:string)

I have few questions regarding this:

1. What is this difference between those two encoding types - xsd and
soapenc? 

2. Which one should I prefer?

3. Does this change in my wsdl file happens because of using a new axis
version? Is it related to web-server configuration? 

 

Thanks for any help,

 

Mati.

 

Re: type mapping: soapenc and xsd

[Anne Thomas Manes <at...@gmail.com>]

This was caused by your upgrade. It was a fix implemented in Axis 1.2. For
interoperability with .NET, you probably want to switch back to the xsd
namespace, although technically, according to the SOAP spec, it should be
the soapenc namespace. (soapenc supports nulls; xsd does not, unless you
specifically add nillable="true" to the type defintion)

To set it back to xsd, add this parameter to your WSDD:
    <parameter name="dotNetSoapEncFix" value="true"/>

Better yet, switch to document/literal wrapped style.

Anne

On 1/29/06, Mati David <ma...@bitband.com> wrote:
>
>  Hi,
>
>
>
> We've just upgraded the axis jar in our project to axis 1.3 from axis 1.1.
>
> After this upgrade the wsdl file (which is automatically generated) has
> different types mapping –
>
> It now somehow uses *soapenc* namespace instead of *xsd* (so for example
> when ever I used to see xsd:string I now see soapenc:string)
>
> I have few questions regarding this:
>
> 1. What is this difference between those two encoding types - *xsd* and *
> soapenc*?
>
> 2. Which one should I prefer?
>
> 3. Does this change in my wsdl file happens because of using a new axis
> version? Is it related to web-server configuration?
>
>
>
> Thanks for any help,
>
>
>
> Mati.
>
>
>