[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reading XML with &Amp; as part of string



   I think that the entities are case sensitive and should be &

   On Tue, Nov 5, 2013 at 3:30 PM, Raul A. Jager W. <[1]raul@xxxxxxxxxx>
   wrote:

     � �%scanrpl('&Amp;': '&': data)

   � �[1][2]Venter.Derick@xxxxxxxxxxxxxx wrote:
   � �Hi there
   � �Hope you can help me.
   � �I am trying to parse an XML document containing the string "&Amp;"
   � �My program just hangs. The parsing works when I remove the &
   character.
   � �The idea is to replace the string "&Amp;" with "&" to get my
   original
   � �string back before saving to the database.
   � �Please help
   � �Regards
   � �Derick Venter
   � �Applications Developer IV

     � �[[2]cid:_4_0A5D33680A5D2F68004D68ED42257C1A]

   � �Systems Integration
   � �Tel: [3]+27 (13) 247 2816 Fax: [4]+27 (0) 86 573 2274
   � �Cell: [5]+27 (0) 83 458 6599

     � �Email: [[3]1][6]derick.venter@xxxxxxxxxx
     � �[2][7]www.gijima.com
     � �From: � � � �Antonio Nalesso [4]<[8]a.nalesso@xxxxxxxxxxx>
     � �To: � � � �HTTPAPI and FTPAPI Projects
     [5]<[9]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>

   � �Date: � � � �2013/11/05 11:28 AM
   � �Subject: � � � �R: HTTPAPI performance

     � �Sent by: � � �     �[6][10]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx

   � �   �__________________________________________________________________
   � �Thanks a lot,
   � �I follow your suggestion so now I see in my log (related to WSS
   DHL for
   � �label request) :
   � �2013-11-05-09.50.39.026000 http_persist_open(): entered
   � � � � � � � � � �Login to remote server
   � �2013-11-05-09.50.41.068000 senddoc(): entered
   � � � � � � � � � �My SOAP request
   � �2013-11-05-09.50.49.698000 SetError() #13: HTTP/1.1 200 OK
   � � � � � � � � � �Server response
   � �So I have 2 seconds to login to DHL server and 8 seconds to have a
   � �reply !!!
   � �Are these times normal for a WSS service ? I have no idea ...
   � �Best regards
   � �Antonio
   � �PS : I use CRTRPGMOD to rebuild HTTPUTILR4. Then I use UPDSRVPGM
   to
   � �update service program, without rebuild it from zero.
   � �-----Messaggio originale-----

     � �Da: [7][11]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �[[3][8]mailto:[12]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] Per
     conto di Mike
     � �Krebs
     � �Inviato: giovedì 31 ottobre 2013 16:40

   � �A: HTTPAPI and FTPAPI Projects
   � �Oggetto: RE: HTTPAPI performance
   � �Earlier this year, I modded my version of the debug log to add
   � �timestamps to the debug. This catches most of the places that
   write to
   � �the debug log but not all, but it will probably give you enough
   � �information to look at.
   � �In HTTPUTILR4 you will find the http_dmsg procedure. Add the
   timestamp
   � �right in the procedure. Here is one way to do it.
   � �c � � � � � � � � � eval � � �wwMsg =
   %char(%timestamp()) + ' ' +
   � �<===mod
   � �c � � � � � � � � � � � � � � � � � �   %trimr(peMsgTxt) + x'0d25'
   � �c � � � � � � � � � eval � � �wwMsgLen =
   %len(%trimr(wwMsg))
   � �c � � � � � � � � � callp � � http_xlate(wwMsgLen:
   wwMsg: TO_ASCII)
   � �Re-install after making the mod by calling the install program.
   � �After the change, the debug log looks like this:
   � �HTTPAPI Ver 1.25beta2 released 2012-03-06
   � �OS/400 Ver V7R1M0
   � �2013-10-31-10.23.19.696000 Setting variables
   � �2013-10-31-10.23.19.715000 http_url_get(): entered
   � �2013-10-31-10.23.19.720000 http_persist_open(): entered
   � �2013-10-31-10.23.19.720000 http_long_ParseURL(): entered
   � �It should give you plenty of data to look at. By modding
   http_dmsg, it
   � �doesn't add timestamps to every message. If you think you have a
   low
   � �level problem, you will need to add timestamps in http_dwrite.
   � �http_dwrite expects ascii so don't forget to do the translation if
   you
   � �go to that level. You will see how in the procedure.
   � �If you are doing "other things" in your code, you might want to
   add
   � �your own debug messages. This would help to tell you that your
   other
   � �stuff is holding up.
   � �http_dmsg('Get system control');
   � �http_dmsg('This is my INCOMING procedure: ' + %trim(name));
   � �http_dmsg('Writing data to file MIKE');
   � �-----Original Message-----

   � �From: [9][13]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   � �[[4][10]mailto:[14]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On
   Behalf Of Antonio
   � �Nalesso
   � �Sent: Thursday, October 31, 2013 6:30 AM

   � �To: [11][15]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
   � �Subject: HTTPAPI performance
   � �Hi ,
   � �I am using HTTPAPI to obtain from DHL WSS labels via web.
   � �The problem is that I am experiencing very long time on response
   (media
   � �11 seconds) and I want to understand where's the problem, that is,
   if
   � �it's mine or related to DHL side.
   � �I put a timestamp before and after the call to "http_url_post_xml"
   but
   � �I not able to understand what happens inside (I try to debug
   HTTPAPIR4
   � �but I loose myself !!!)
   � �There is any way to obtain the time of response from remote server
   ?
   � �For example : how much time to obtain connection, how much time to
   � �obtain answer, and so on ....
   � �I have the debug always *on, but nothing change turning it off.
   � �PS : I am problem in searching inside FTPAPI archives ... Search
   give
   � �me always no results, but ifI go inside the specific month I found
   it
   � �!!! Example : I search for 'DHL' : result 0 .
   � �If I went inside June 2012 I found "Consuming DHL Webservices"
   that I
   � �discover via Google !
   � �Best regards
   � �Nalesso Antonio
   �   �---------------------------------------------------------------------
   --
   � �This is the FTPAPI mailing list. �To unsubscribe, please go to:

     � �[5][12][16]http://www.scottklement.com/mailman/listinfo/ftpapi

   �   �---------------------------------------------------------------------
   --
   �   �---------------------------------------------------------------------
   --
   � �This is the FTPAPI mailing list. �To unsubscribe, please go to:

     � �[6][13][17]http://www.scottklement.com/mailman/listinfo/ftpapi

   �   �---------------------------------------------------------------------
   --
   � �   �__________________________________________________________________
   � �This e-mail is subject to the Columbus Stainless [Pty] Ltd Email
   Legal
   � �Notices available at:

     � �[7][14][18]http://www.columbus.co.za/EmailLegalNotice.htm.

   � �   �__________________________________________________________________
   � �This e-mail message has been scanned for Viruses and Content and
   � �cleared by MailMarshal
   � �   �__________________________________________________________________
   References

     � �1. [15]mailto:[19]derick.venter@xxxxxxxxxx
     � �2. [16][20]http://www.gijima.com/
     � �3. [17]mailto:[21]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �4. [18]mailto:[22]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �5. [19][23]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �6. [20][24]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �7. [21][25]http://www.columbus.co.za/EmailLegalNotice.htm
     � �     ____________________________________________________________________
     ____

   -----------------------------------------------------------------------
   This is the FTPAPI mailing list. �To unsubscribe, please go to:

     [22][26]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---
     References
     � �1. mailto:[27]Venter.Derick@xxxxxxxxxxxxxx
     � �2. cid:_4_0A5D33680A5D2F68004D68ED42257C1A
     � �3. mailto:[28]1][29]derick.venter@xxxxxxxxxx
     � �4. mailto:[30]a.nalesso@xxxxxxxxxxx
     � �5. mailto:[31]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
     � �6. mailto:[32]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �7. mailto:[33]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �8. mailto:[34]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �9. mailto:[35]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � 10. mailto:[36]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � 11. mailto:[37]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
     � 12. [38]http://www.scottklement.com/mailman/listinfo/ftpapi
     � 13. [39]http://www.scottklement.com/mailman/listinfo/ftpapi
     � 14. [40]http://www.columbus.co.za/EmailLegalNotice.htm
     � 15. mailto:[41]derick.venter@xxxxxxxxxx
     � 16. [42]http://www.gijima.com/
     � 17. mailto:[43]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � 18. mailto:[44]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � 19. [45]http://www.scottklement.com/mailman/listinfo/ftpapi
     � 20. [46]http://www.scottklement.com/mailman/listinfo/ftpapi
     � 21. [47]http://www.columbus.co.za/EmailLegalNotice.htm
     � 22. [48]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---
     This is the FTPAPI mailing list. �To unsubscribe, please go to:
     [49]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---

   --
   Regards,
   Henrik Rützou
   �   [50]http://powerEXT.com
   �
References

   1. mailto:raul@xxxxxxxxxx
   2. mailto:Venter.Derick@xxxxxxxxxxxxxx
   3. tel:%2B27%20%2813%29%20247%202816
   4. tel:%2B27%20%280%29%2086%20573%202274
   5. tel:%2B27%20%280%29%2083%20458%206599
   6. mailto:derick.venter@xxxxxxxxxx
   7. http://www.gijima.com/
   8. mailto:a.nalesso@xxxxxxxxxxx
   9. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
  10. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  11. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  12. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  13. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  14. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  15. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
  16. http://www.scottklement.com/mailman/listinfo/ftpapi
  17. http://www.scottklement.com/mailman/listinfo/ftpapi
  18. http://www.columbus.co.za/EmailLegalNotice.htm
  19. mailto:derick.venter@xxxxxxxxxx
  20. http://www.gijima.com/
  21. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  22. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  23. http://www.scottklement.com/mailman/listinfo/ftpapi
  24. http://www.scottklement.com/mailman/listinfo/ftpapi
  25. http://www.columbus.co.za/EmailLegalNotice.htm
  26. http://www.scottklement.com/mailman/listinfo/ftpapi
  27. mailto:Venter.Derick@xxxxxxxxxxxxxx
  28. mailto:1
  29. mailto:derick.venter@xxxxxxxxxx
  30. mailto:a.nalesso@xxxxxxxxxxx
  31. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
  32. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  33. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  34. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  35. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  36. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  37. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
  38. http://www.scottklement.com/mailman/listinfo/ftpapi
  39. http://www.scottklement.com/mailman/listinfo/ftpapi
  40. http://www.columbus.co.za/EmailLegalNotice.htm
  41. mailto:derick.venter@xxxxxxxxxx
  42. http://www.gijima.com/
  43. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  44. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
  45. http://www.scottklement.com/mailman/listinfo/ftpapi
  46. http://www.scottklement.com/mailman/listinfo/ftpapi
  47. http://www.columbus.co.za/EmailLegalNotice.htm
  48. http://www.scottklement.com/mailman/listinfo/ftpapi
  49. http://www.scottklement.com/mailman/listinfo/ftpapi
  50. http://powerext.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------