Re: How to not send nillable="true" for null elements in a SOAP message

[Tim R J Langford]

Thanks Rod,

I agree with you and will handle it this way.

Thankyou everyone for your help and advice,

Tim


Rodrigo Ruiz wrote:

By what you describe, I think you should add minOccurs='0' and remove nillable='true'

Regards,
Rodrigo Ruiz

Tim R J Langford wrote:

Thanks Anne,

Thats what I thought. Unfortunatly our provider does not seem too clued up on their tech, and the wsdl does not allow minOccurs="0". I guess I will have to update our automated build process to fix their schema before generating my soap beans and classes. The best way to do this would be by adding minOccurs="0" to the faulty elements I presume?

Thanks to everybody for their time,

Tim


Anne Thomas Manes wrote:

If the service cannot accept xsi:nil="true" then the service provider should adjust the schema accordingly. Does the schema allow minOccurs="0"? If not, then there's no valid way to send no element instead of xsi:nil="true".

Anne

On 2/14/06, *Tim R J Langford* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi Jeff,

    Thanks for your response.

    Sorry for being unclear. Yes you are correct. I am sending

'xsi:nil="true"' and I want to configure axis to send nothing instead

    of this string.  e.g : *

    <XXX* xsi:type="xsd:string" xsi:nil="true"/>*
    <YYY* xsi:type="zzz:YYY" xsi:nil="true" xmlns:zzz="KKK"*/>

    *I think Axis 1.2 did it this way? Is there anyway of configuring
    Axis
    1.3 to not send these 'xsi:nil="true"' elements?

    Thanks for you time,

    Tim

PS: The service wsdl does have 'xsd:nillable="true"' elements in the message schema, but their system cannot actually handle the situation where it is null (even if they return it in a response), and they have asked us to remove the 'xsi:nil="true"' elements from our requests. We

    could fix the wsdl schema, but this would impede our codegen
    system as

we are the client, so were wondering if there was a way to do it from

    within axis?*



    *

    Jeff Greif wrote:

    >Just to be sure, you're sending xsi:nil="true", not
    xsd:nillable="true", right?
    >

>The latter is used only in the schema, and means that the element is

    >allowed to have no content.  The former means that this
    particular use
    >of the element has no content.
    >
    >Jeff
    >
    >On 2/14/06, Tim R J Langford <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
    >
    >
    >>Hello All,
    >>
    >>I am writing a client interface into a provider SOAP web
    service, and
    >>their system fails and returns a null pointer exception when I
    send them
    >>a 'nillable="true"' element in my request. I think the reason
    for this
    >>is that they are using an older version of axis than we are
    using ( 1.3).
    >>
    >>
    >
    >
    >