miraclebabycaw
New Member
Hi all
Wondering if anyone can help. I am exporting an XML document thru a WSDL. We export the XML to a file at the same time for checking. The code to set the attributes is:
hreturn:CREATE-NODE(h1stlevel, "DOCUMENT", "ELEMENT").
hreturn:APPEND-CHILD(h1stlevel).
h1stlevel:SET-ATTRIBUTE("version", "3.0").
h1stlevel:SET-ATTRIBUTE("reply_tp", "1").
no matter what we do this always places the reply_tp attribute before the version attribute. Now you would think it wouldn't matter but for some reason the 3rd party we send it to has no issues with the rest of the code setting the attributes in alphabetical order, but they do with this. I don't know why but we need to fix it so that the reply will go sitting after the version attribute.
Any ideas anyone?
Wondering if anyone can help. I am exporting an XML document thru a WSDL. We export the XML to a file at the same time for checking. The code to set the attributes is:
hreturn:CREATE-NODE(h1stlevel, "DOCUMENT", "ELEMENT").
hreturn:APPEND-CHILD(h1stlevel).
h1stlevel:SET-ATTRIBUTE("version", "3.0").
h1stlevel:SET-ATTRIBUTE("reply_tp", "1").
no matter what we do this always places the reply_tp attribute before the version attribute. Now you would think it wouldn't matter but for some reason the 3rd party we send it to has no issues with the rest of the code setting the attributes in alphabetical order, but they do with this. I don't know why but we need to fix it so that the reply will go sitting after the version attribute.
Any ideas anyone?