[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Soap Question
Some of our internal systems can't handle Grave or Tilde characters, so
we clean up the data before sending it out. This is a subprocedure we
use to convert special characters to English equivalents.
* Convert special characters
d convert PR 100a varying
d data 100a varying const options(*trim)
xmli_setParm(3 : convert(guestName));
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
// procedure for converting special characters
//++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
p convert B
d convert PI 100a varying
d data 100a varying const options(*trim)
d results s 100a varying inz('')
d from c
x'654571517555EECEFEDEAD8D- Acute
d
624272527656EBCBFBDB- Circumflex
d 644474547858EDCDFDDD-
Grave
d
6646EFCF6949- Tilde
d
634373537757ECCCFCDCFFDF- Umlaut
d 59674768488070'
Other
d to c
x'C181C585C989D696E4A4E8A8- Acute
d
C181C585C989D696E4A4- Circumflex
d
C181C585C989D696E4A4- Grave
d
C181D696D595- Tilde
d
C181C585C989D696E4A4E8A8- Umlaut
d C2C181C383D696'
Other
results = %xlate(from :to : data);
return results;
p E
Paul
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jim Muehe
Sent: Friday, April 10, 2015 10:24 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Soap Question
Just worried about garbage.
Doing SOAP to generate Order Confirmation emails -- who knows what kind
of garbage gets put into the web.
Jim Muehe
-----Original Message-----
From: [1]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[2]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike
Krebs
Sent: Friday, April 10, 2015 10:03 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Soap Question
I do not think any of the EXAMPLE programs show special encoding. It is
not needed in most cases.
Just create your SOAP message and send it. See what happens!
What kind of encoding do you think you need? The archives contain
discussions about various types of problems others have encountered.
Since I am unsure of what type of encoding you think you will need, I
am unsure where to point you to.
-----Original Message-----
From: [3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[4]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jim
Muehe
Sent: Friday, April 10, 2015 9:50 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Soap Question
Mike,
Are there any tools in the HTTPAPI that would work for encoding SOAP's
Example on how to use it?
Jim Muehe
-----Original Message-----
From: [5]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[6]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike
Krebs
Sent: Thursday, April 09, 2015 4:56 PM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Soap Question
This represents an evolution of the tool. Like the examples, most SOAP
messages sent using http_url_post_xml can be sent without further
encoding, escaping, or translation.
Web data (that intended to be displayed) needs a way to tell a < from a
<. Unless you expect your xml values to have xml tags in it, you
should not have a problem with this. If you are transferring or
receiving xml tags as data values (not as tags), you might have to code
for them but that should be apparent as you know what your data is.
-----Original Message-----
From: [7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[[8]mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Jim
Muehe
Sent: Thursday, April 9, 2015 4:07 PM
To: [9]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: Soap Question
Hello,
I have used http_url_post_xml but in conjunction with the WEBFORM &
http_url_encoder_addvar Now I need to do a SOAP. In the samples I did
not see that it was encoded Does it need to be? Easiest way to do it?
This might be a stupid question, but I am pretty ignorant on this
stuff.
Jim Muehe | Sr. Programmer Analyst | CHEFS(r) | An Affiliate of *Target
Corporation(r) | 5070 Centennial Blvd. | Colorado Springs, CO 80919
719.272.2618 (P) | 719.272.2624 (F) |
[10]www.CHEFScatalog.com<http://www.chefscatalog.com/> |
[11]www.Target.com<http://www.target.com/>
________________________________
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient(s), please contact the sender by reply e-mail and destroy all
copies of the original message.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[12]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
________________________________
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient(s), please contact the sender by reply e-mail and destroy all
copies of the original message.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[13]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[14]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
________________________________
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient(s), please contact the sender by reply e-mail and destroy all
copies of the original message.
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[15]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
The information contained in this message is confidential and intended
only for the use of the individual or entity named above, and may be
privileged. Any unauthorized review, use, disclosure, or distribution
is prohibited. If you are not the intended recipient, please reply to
the sender immediately, stating that you have received the message in
error, then please delete this e-mail. Thank you.
References
1. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
5. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
6. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
10. http://www.CHEFScatalog.com%3chttp:/www.chefscatalog.com/
11. http://www.Target.com%3chttp:/www.target.com/
12. http://www.scottklement.com/mailman/listinfo/ftpapi
13. http://www.scottklement.com/mailman/listinfo/ftpapi
14. http://www.scottklement.com/mailman/listinfo/ftpapi
15. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------