XSD nillable element support

[Former Member]

Hi,

I need to set explicitly null elements using xsd:nil="true" attribute.

It seems that the nillable element is accepted when I am importing my WSDL but I can't access it in the mapping tool (required to be used vs JAVA/ABAP mappings).

Would you have any suggestion to produce the xsd:nil="true" attribute in the target message?

Thanks,

Adalbert

[Former Member]

Have you tried making the same attribute in a test DT and seeing the code which comes out, and compare it to your code?

[Former Member]

Hey Paul,

Actually I am expecting having a native support of this attribute taken from the XML Schama or WSDL.

I know that I can import a sample message as target in a mapping with this attribute defnied and the tool will present the attribute for mapping... but I need to work from XMLSchema and WSDL and not from samples messages.:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pur="http://mynamespace"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soapenv:Header/>

<soapenv:Body>

<pur:MT_RequestType xsd:nil="true">

<SystemID>TOTO</SystemID>

</pur:MT_RequestType>

</soapenv:Body>

</soapenv:Envelope>

Do you expect something different from the operation you suggested?

Thanks,

Adalbert

[Former Member]

Hi Adalbert,

your document is incorrect. It should read

<pur:MT_RequestType xsi:nil="true"> with prefix xsi bound to the namespace http://www.w3.org/2001/XMLSchema-instance

(In fact you do not have to switch to prefix

<i>xsd</i>, you could stay with <i>xsd</i> but would have to bind this prefix to namespace http://www.w3.org/2001/XMLSchema-instance, but this would be irritating to human readers).

Unfortunately, even after having corrected your document this way, the graphical mapping tool will not support you. There is no support for that feature in the mapping tool.

Greetings

Stephan

[Former Member]

Thanks Stephan for your response.