Re: SOAPAction and Unmarshal Exception

[Scott Klement <klemscot@xxxxxxxxxxxx>]

Hi Erin,

Your debug log (the one you attached) seems to show SoapAction: "", just 
as you expected, which confuses me because the text of your e-mail 
states that it's not blank in the debug log...?

SoapAction is just a parameter that can be read by the web service and 
used to control how it operates.  Sometimes multiple web services run on 
the same URL.  The SOAP action helps distinguish between them.

 From the consumer's perspective, it's just a matter of passing the soap 
action that the provider is expecting -- it doesn't really matter what 
it is.  Just pass what it tells you to pass.

Try using a tool like SoapUI to interpret your WSDL, if you're having 
trouble.  Though, the error message you posted doesn't appear to be 
related to the SoapAction as far as I can tell.  Rather, it looks like a 
namespace issue -- at least that's the way I read it.



EStrobel@xxxxxxxxxxxxxxxx wrote:
>    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/RPGTestServic
>    e/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 is the FTPAPI mailing list.  To unsubscribe, please go to:
> 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
-----------------------------------------------------------------------