NetTalk Central

Author Topic: WSDL seems to cut off fieldnames arbitrarily  (Read 5145 times)

Wolfgang Orth

  • Sr. Member
  • ****
  • Posts: 251
    • View Profile
    • oData Wolfgang Orth
WSDL seems to cut off fieldnames arbitrarily
« on: September 27, 2018, 12:26:43 AM »
Hello Bruce,

apparently the template, that generates the WSDL, cuts off the Fieldnames at the Underscore, turning lfdNr_A to A, as seen below.

<Rueckgabe_list>
        <Paarung>
          <SYSID>value</SYSID>
          <lfdNr_A>value</lfdNr_A>
          <PZN_A>value</PZN_A>
          <Produktname_A>value</Produktname_A>
          <lfdNr_B>value</lfdNr_B>
          <PZN_B>value</PZN_B>
          <Produktname_B>value</Produktname_B>
          <Inkompatibilitaetsstatus>value</Inkompatibilitaetsstatus>
          <HTMLKommentar>value</HTMLKommentar>
        </Paarung>

<xs:complexType name="Rueckgabe">
<xs:sequence>
<xs:element minOccurs="0" name="SYSID" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="Inkompatibilitaetsstatus" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="HTMLKommentar" nillable="false" type="xs:string"/>
</xs:sequence>

As far as I understood, the NT--templates treat the colonm, being the separator between prefix and label, by converting to an underscore. This WSDL-generator seems to believe, that everything left of the underscore is the prefix and <TSCHACK> chops if off with its eversharp hatchet. maybe I am wrong, this is just how I think its working at the moment.

I will now circumvent this by renaming these fields. It would be nice, if this could be addressed somehow, either by leaving the labelname as it is, cuts off only the prefix, or by mentioning this in the manual, like "Never use an underscore in the fieldnames!".

Thanks
Wolfgang

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: WSDL seems to cut off fieldnames arbitrarily
« Reply #1 on: September 30, 2018, 10:09:32 PM »
Hi Wolfgang,

which build of NetTalk and xFiles are you using?
I think this issue has long-since been dealt with. (but possibly not.)

cheers
Bruce

Wolfgang Orth

  • Sr. Member
  • ****
  • Posts: 251
    • View Profile
    • oData Wolfgang Orth
Re: WSDL seems to cut off fieldnames arbitrarily
« Reply #2 on: September 30, 2018, 10:58:02 PM »
Hi Wolfgang,

which build of NetTalk and xFiles are you using?
I think this issue has long-since been dealt with. (but possibly not.)

cheers
Bruce

Good Morning Bruce,

sorry for once again forgetting to tell the version number!

Nettalk 9.30 (frozzen for this project)
xFiles 2.89
Stringtheory 2.74

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: WSDL seems to cut off fieldnames arbitrarily
« Reply #3 on: October 01, 2018, 07:34:31 AM »
>> Nettalk 9.30 (frozen for this project)

cool. I think it's been fixed already.

Cheers
Bruce