[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: SOAPAction and Unmarshal Exception
Erin,
You can use http_xproc to register a procedure which you can define a
longer SoapAction value. It works for me, see the following code:
D Add_SoapAction PR
D Header 1024A Varying
D UserData * Value
D cMode C 'text/xml; charset=utf-8'
http_xproc( HTTP_POINT_ADDL_HEADER
: %Paddr(Add_SoapAction));
nRC = http_url_post_stmf( xWsurl
: %Trim(xFilePath) + '/' + cTempFile
: %Trim(xFilePath) + '/' + cResultFile
: HTTP_TIMEOUT
: HTTP_USERAGENT
: cMode);
P Add_SoapAction B
D Add_SoapAction PI
D xHeader 1024A varying
D xUserData * value
D cAction C 'https://services.scanhealthplan.-
D com/EncryptByClientPublicKeyName-
D Base64'
/free
xHeader = 'SOAPAction: ' + cAction + cCrLf;
Return;
/end-free
P E
Thanks,
Donald Leong
Phone# (562) 989-5165
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
EStrobel@xxxxxxxxxxxxxxxx
Sent: Wednesday, December 31, 2008 12:47 PM
To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Subject: SOAPAction and Unmarshal Exception
I have a couple questions regarding SOAPAction and an Unmarshal
Exception
I'm receiving in calling my web service. I've attached the complete
debug
log, source code for my program, and can provide the WSDL if needed.
SOAPAction:
How do I know what needs to go in the SOAPAction parameter for the
http_url_post_xml and what is it really?
In the WSDL for my web service, I see this: <soap:operation
soapAction=""/>, so that's what I put in the parameter because it
coincides with Examples 18 and 19. However, in debug log, I'm noticing
this:
...
User-Agent: http-api/1.23
Content-Type: text/xml; charset=utf-8
SOAPAction:
http://sandbox.ad.churchmutual.com:35100/RPGAccessRefApp/RPGTest
Expect: 100-continue
Content-Length: 330
...
The SOAPAction value if anything should be
http://sandbox.ad.churchmutual.com:35100/RPGAccessRefApp/RPGTest
Service/TestMethodForRPG
but is too long for the parameter (parm is only set to be 64 alpha and
this is 88), hence why it's cut off in the log. How do I know which
value
is correct? And if the latter is correct, do I change all the
definitions
in the HTTPAPI to be longer than 64 or is there another way?
Unmarshal Exception - unexpected element:
I've attached the debug log so you can see the exception. Is this being
caused by the SOAPAction thing or is this something else? Any ideas?
Erin L Strobel
Information Services - Programmer
Church Mutual Insurance
1-800-554-2642 Ext. 4947
==========================================
This communication contains information that is confidential, and solely for the use of the intended recipient. It may contain information that is privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this communication, please be advised that any disclosure, copying, distribution or use of this communication is strictly prohibited. Please also immediately notify SCAN Health Plan at 1-800-247-5091, x5263 and return the communication to the originating address.
Thank You.
==========================================
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------