Re: Optional fields in Xml message for SOAP Web Service -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Optional fields in Xml message for SOAP Web Service
From: Alasdair Macdonald <wewalkforonereason@xxxxxxxxx>
Date: Fri, 17 Jun 2016 19:17:32 +0100
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

The former.

On 17 June 2016 at 19:12, pat <p.caroti@xxxxxxxx> wrote:

Hi all

i would need to know how to generate an Xml message for optional fields

suppose that i have an optional fields minOccurs="0", example;
<xs:element name="errorCode" type="xs:string" minOccurs="0"/>

if there is not any valu to pass for errorCode, in my Xml
i don't have to write the row or i can/have to write
<errorCode></errorCode>

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Optional fields in Xml message for SOAP Web Service , pat

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.