Re: SOAPAction required?

[Justin Schoeman]

From what I can understand, the empty string is deliberate. The service is supposed to call the correct operation for the supplied message. The SOAP documentation lists SOAPAction as required, but may be "" if no additional message routing information is required.

wsdl file:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl

xsd files:
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-base-2.0.xsd
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-revenue-2.0.xsd
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/Schema/xmlvend-meter-2.0.xsd

Example request message:
(attached in t.pl)

Thanks,
Justin

Amila Suriarachchi wrote:

I think here the problem is that this wsdl (http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl <http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl>) has an empty string as soapaction (i.e. soapaction = "")

and it is document type.

Can you attached the two requests generated by the axis2 and .net client?



Thanks
 Amila

I could not generate the client/server since I could not find the location for the .xsd files. On 1/10/07, *Deepal Jayasinghe* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi Justin ;

    Yes if you are using SOAP 1.2 , then the SOAP action is optional. Anyway
    please send us the wsdl file so that we can try to find the issue.

    Thanks
    Deepal

     > I am busy testing an application at the moment (against the 9
    January
     > snapshot).
     >
     > When I test with an AXIS2 generated client, all works fine, but when
     > testing with a .Net client, I get an 'The endpoint reference
    (EPR) for
     > the Operation not found is
     > http://192.168.1.10:8080/axis2/services/XMLVendService2.0 and the WSA
     > Action = ' error.
     >
     > Reading the SOAP documentation on the SOAPAction/action parameter:
     >  "The presence and content of the action parameter MAY be used by
     > servers such as firewalls to appropriately filter SOAP messages
    and it
     > may be used by servers to facilitate dispatching of SOAP messages to
     > internal message handlers etc. It SHOULD NOT be used as an insecure
     > form of access authorization.
     >
     > Use of the action parameter is OPTIONAL. SOAP Receivers MAY use it as
     > a hint to optimize processing, but SHOULD NOT require its
    presence in
     > order to operate."
     >
     > It seems as though it should be acceptable to send the request with
     > SOAPAction "", but it seems not to be allowed by AXIS2. Or am I doing
     > something wrong?
     >
     > WSDL file is provided by a commercial organisation, and is claimed to
     > be correct:
     >
    
http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl
    
<http://nrs.eskom.co.za/xmlvend/docs/Specification/November2005/WSDL/xmlvend-full-2.0.wsdl>
     >
     >
     > Thanks,
     > Justin
     >
     > ---------------------------------------------------------------------
     > To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
     > For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
     >
     >
     >

    --
    Thanks,
    Deepal
    ................................................................
    "The highest tower is built one brick at a time"



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>




--
Amila Suriarachchi,
WSO2 Inc.

t.pl
Description: Perl program

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]