× 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.





I changed the http_url_post_stmf parameter for the XML file to a %trim(#filename) and that corrected the quote issue.  The quote was there, but way out of place...



I've gone through the http_debug.txt file to see if there were any other missing marks. Nothing.



I'm including part of the post data (I cut it off as it does have some confidential stuff..)



---httpapi-2013-07-11-14.14.17.204
Content-Disposition: form-data; name="code"

johnnyjanosik                                                                  
---httpapi-2013-07-11-14.14.17.204
Content-Disposition: form-data; name="api_key"

f10edfb635f01daad                                                              
---httpapi-2013-07-11-14.14.17.204
Content-Disposition: form-data; name="data"; filename="/routing/xmldispatch5_TEST.xml"
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<service_orders>
<service_order>
<number>1-610615</number>
<account>231196</account>
<service_type>Delivery</service_type>
<customer>
  <customer_id>231196</customer_id>
  <first_name>BONNIE</first_name>


The XML generated is paired up correctly with information.




----- Original Message -----


From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, July 11, 2013 10:01:35 AM
Subject: Re: http_url_post_xml and REST

That's possible -- could be the encoding.

But, another possibility is that the missing quote on the filename is
causing the web service to interpret the start of the XML data as part
of the filename (up until the first quote mark found in the XML data --
in the XML version)  If that happened, the first characters it'd see in
the XML document would be the "1.0", which would also trigger the error
that Jay cited.

So, I think he should check both things... That quote is not optional,
he needs to find out why it's missing.

And, he needs to make sure the XML is in the proper encoding, too.

-SK


On 7/11/2013 1:44 AM, thomas.raddatz@xxxxxx wrote:

For me the error message implies that you do not send the XML in UTF-8 but
any other encoding. That way the server can not find the "<" character at
the first position of the XML.

The error message:

    <?xml version="1.0" encoding="UTF-8"?><error>XML Error: Fatal error:
    Start tag expected, '&lt;' not found at :1.</error>

What the server tries to read:

    <?xml version="1.0" encoding="UTF-8"?>
    <service_orders>

Because of the wrong encoding it can not find the "<" of "<?xml ...".

Nothing more than a guess.

Thomas.

rpg400-l-bounces@xxxxxxxxxxxx schrieb am 10.07.2013 21:53:58:

Von: tegger@xxxxxxxxxxx
An: rpg400-l@xxxxxxxxxxxx,
Datum: 10.07.2013 21:54
Betreff: Re: http_url_post_xml and REST
Gesendet von: rpg400-l-bounces@xxxxxxxxxxxx



I have that in there. Thanks though!

I hard coded it just during my original attempts to get it running.



It's running now. Just have an error with the XML (or their server
says there's an error).



I was looking in the httpapi_debug.txt file and noticed that the
filename line is missing a double quote at the end of the filename.
I doubt that is causing my issue...


<?xml version="1.0" encoding="UTF-8"?><error>XML Error: Fatal error:
Start tag expected, '&lt;' not found at :1.</error>


<?xml version="1.0" encoding="UTF-8"?>
<service_orders>
<service_order>
<number>1-610615B</number>
<account>2311960</account>
<service_type>Delivery</service_type>
<customer>
<customer_id>2311960</customer_id>
<first_name>HENRY</first_name>
<last_name>MILLER</last_name>
<phone1>301-555-1212</phone1>
<phone2>301-555-1213</phone2>
<address1>SOME STREET</address1>
<city>BOWIE</city>
<state>MD</state>
<zip>20716</zip>
</customer>
<items>
<item>
<sale_sequence>1</sale_sequence>
<item_id>1055746</item_id>
<serial_number>001999188</serial_number>
<description><![CDATA[P992050BD SOFA PAULA DEEN SOLITUDE 09/CW BRO
NCO 31/BOL LENA 22/PIL RE]]></description>
<quantity>1</quantity>
<location>Warehouse#1</location>
<cube>3</cube>
<price>1334.95</price>
<countable>1</countable>
</item>
</items>
<cube>1</cube>
<pieces>1</pieces>
<delivery_date>7/09/2014</delivery_date>
</service_order>
</service_orders>



----- Original Message -----


From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-
l@xxxxxxxxxxxx>
Sent: Wednesday, July 10, 2013 2:39:02 PM
Subject: Re: http_url_post_xml and REST

Jay,

I know you've gotten past this point already, but... one tip for you
with regard to the following code:


if (rc <> 1);
      msg = http_error(err);
      dsply msg;
      if err<>36;
         callp http_crash();
         return;
      endif;
      exsr $getPassword;
endif;


There are named constants in HTTPAPI_H for each error number.  So
instead of coding err<>36, you could code err<>HTTP_NDAUTH.  This is
just easier to read...  HTTP_NDAUTH visually looks like 'Need
Authentication", whereas it's hard to say what '36' means.  Even I
didn't know what it was without looking it up...

It's just a small tip, though... what you have will work okay, it's just

not as nice to read.
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a criminal
offence. Please delete if obtained in error and email confirmation to the sender.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.