|
On Mar 3, 2020, at 7:57 AM, Maria Lucia Stoppa <mlstoppa@xxxxxxxxx> wrote:
I found a workaround, it doesn't explain why but this way data can be
retrieved without error: instead of zoned the subfield TotaleColli is now
defined char.
Does this make sense?
Il giorno mar 3 mar 2020 alle ore 10:35 Maria Lucia Stoppa <
mlstoppa@xxxxxxxxx <mailto:mlstoppa@xxxxxxxxx>> ha scritto:
Hello,
I am successfully using xml-into in many applications, but sometimes the
XML answer of a web service is like this:
<?xml version="1.0" encoding="utf-8"?>
<InfoLabel>
<Parcel>
<SiglaMittente>E3</SiglaMittente>
<NumeroSpedizione>800000009</NumeroSpedizione>
<TotaleColli>11</TotaleColli>
<TipoCollo />
<SiglaSedeDestino />
<DenominazioneMittente>GLS BOLOGNA</DenominazioneMittente>
<DenominazioneDestinatario>PROVA ETICHETTE</DenominazioneDestinatario>
<IndirizzoDestinatario>VIA DEL FONDITORE 2/7</IndirizzoDestinatario>
<CittaDestinatario>MILANO</CittaDestinatario>
<ProvinciaDestinatario>MI</ProvinciaDestinatario>
<DataSpedizione>03/03/20</DataSpedizione>
<DescrizioneSedeDestino>GLS Check</DescrizioneSedeDestino>
...other xml data..
</Parcel>
<Parcel>
...other xml data..
</Parcel>
</InfoLabel>
where the difference is the presence of self-closing tags (likeTipoCollo
in the example). Other web services usually return both opening and closing
tags with a blank inside.
When xml-into is executed it breaks with this error:
RNX0353 - The XML document does not match the RPG variable; reason code 8.
where
8. The XML document contains data that cannot be successfully assigned to
the RPG variable. The RPG status code associated with the failure is 105.
The exact subfield for which the error was detected is
"infolabel.parcel(1).tipocollo"
The data structure is defined like this:
dcl-ds DsInfoLabel qualified inz;
SiglaMittente char(2) inz;
NumeroSpedizione zoned(9: 0) inz;
TotaleColli zoned(2: 0) inz;
TipoCollo zoned(1: 0) inz;
SiglaSedeDestino char(4) inz;
... other fields...
end-ds;
dcl-ds InfoLabel qualified inz;
NumParcel int(10) inz;
Parcel likeds(DsInfoLabel) dim(99);
end-ds;
This is the operation code:
xml-into(e) InfoLabel %xml(resmsg_DATA: xmlopts);
where
xmlopts='doc=string trim=all case=any allowmissing=yes allowextra=yes
path=InfoLabel countprefix=Num'
As far as I know, there isn't any other option that can be set to avoid
this situation.
Also, this web service must be used as-is.
Is there something else I can do??
Thank you
--
Maria Lucia Stoppa
mlstoppa@xxxxxxxxx
--
Maria Lucia Stoppa
mlstoppa@xxxxxxxxx <mailto:mlstoppa@xxxxxxxxx>
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.