SOAPAction header problem...Urgent

Hi to All
I am using WAS v6.1 for deploy webservice(soap1.1).My java webservice get a call from .net(its like client).Here i am facing the problem like,
when i add my java webservice as "service reference" to .net(visual studio2005+sdk v2.0 framework)..its throwing "No SOAPAction header" found error.

java wsdl deployed in was6.1 with out errors.but at .net end its throwing the above error..from trace log i found that

[10/31/07 10:27:59:658 IST] 0000001e MessageTrace 3 WSWS3569I: Inbound HTTP SOAP request:
Content-Type: application/soap+xml; charset=utf-8
Message contents:

0000: 3C 73 3A 45 6E 76 65 6C - 6F 70 65 20 78 6D 6C 6E <s:Envelope xmln
0010: 73 3A 73 3D 22 68 74 74 - 70 3A 2F 2F 77 77 77 2E s:s="http://www.
0020: 77 33 2E 6F 72 67 2F 32 - 30 30 33 2F 30 35 2F 73 w3.org/2003/05/s
0030: 6F 61 70 2D 65 6E 76 65 - 6C 6F 70 65 22 20 78 6D oap-envelope" xm
0040: 6C 6E 73 3A 61 3D 22 68 - 74 74 70 3A 2F 2F 77 77 lns:a="http://ww
0050: 77 2E 77 33 2E 6F 72 67 - 2F 32 30 30 35 2F 30 38 w.w3.org/2005/08
0060: 2F 61 64 64 72 65 73 73 - 69 6E 67 22 3E 3C 73 3A /addressing"><s:
0070: 48 65 61 64 65 72 3E 3C - 61 3A 41 63 74 69 6F 6E Header><a:Action
0080: 20 73 3A 6D 75 73 74 55 - 6E 64 65 72 73 74 61 6E s:mustUnderstan
0090: 64 3D 22 31 22 3E 68 74 - 74 70 3A 2F 2F 73 63 68 d="1">http://sch
00A0: 65 6D 61 73 2E 78 6D 6C - 73 6F 61 70 2E 6F 72 67 emas.xmlsoap.org
00B0: 2F 77 73 2F 32 30 30 34 - 2F 30 39 2F 74 72 61 6E /ws/2004/09/tran
00C0: 73 66 65 72 2F 47 65 74 - 3C 2F 61 3A 41 63 74 69 sfer/Get</a:Acti
00D0: 6F 6E 3E 3C 61 3A 4D 65 - 73 73 61 67 65 49 44 3E on><a:MessageID>
00E0: 75 72 6E 3A 75 75 69 64 - 3A 35 34 62 65 65 38 34 urn:uuid:54bee84
00F0: 38 2D 33 33 65 37 2D 34 - 35 66 64 2D 61 35 30 31 8-33e7-45fd-a501
0100: 2D 30 64 39 66 38 64 63 - 30 30 31 38 34 3C 2F 61 -0d9f8dc00184</a
0110: 3A 4D 65 73 73 61 67 65 - 49 44 3E 3C 61 3A 52 65 :MessageID><a:Re
0120: 70 6C 79 54 6F 3E 3C 61 - 3A 41 64 64 72 65 73 73 plyTo><a:Address
0130: 3E 68 74 74 70 3A 2F 2F - 77 77 77 2E 77 33 2E 6F >http://www.w3.o
0140: 72 67 2F 32 30 30 35 2F - 30 38 2F 61 64 64 72 65 rg/2005/08/addre
0150: 73 73 69 6E 67 2F 61 6E - 6F 6E 79 6D 6F 75 73 3C ssing/anonymous<
0160: 2F 61 3A 41 64 64 72 65 - 73 73 3E 3C 2F 61 3A 52 /a:Address></a:R
0170: 65 70 6C 79 54 6F 3E 3C - 61 3A 54 6F 20 73 3A 6D eplyTo><a:To s:m
0180: 75 73 74 55 6E 64 65 72 - 73 74 61 6E 64 3D 22 31 ustUnderstand="1
0190: 22 3E 68 74 74 70 3A 2F - 2F 76 72 61 6A 61 6D 61 ">http://vrajama
01A0: 6E 69 63 31 2E 61 73 69 - 61 70 61 63 69 66 69 63 nic1.asiapacific
01B0: 2E 68 70 71 63 6F 72 70 - 2E 6E 65 74 3A 39 30 38 .hpqcorp.net:908
01C0: 31 2F 44 79 6E 61 6D 69 - 63 57 65 62 2F 73 65 72 1/DynamicWeb/ser
01D0: 76 69 63 65 73 2F 53 61 - 6D 70 6C 65 45 4A 42 2F vices/SampleEJB/
01E0: 77 73 64 6C 2F 53 61 6D - 70 6C 65 45 4A 42 2E 77 wsdl/SampleEJB.w
01F0: 73 64 6C 2F 6D 65 78 3C - 2F 61 3A 54 6F 3E 3C 2F sdl/mex</a:To></
0200: 73 3A 48 65 61 64 65 72 - 3E 3C 73 3A 42 6F 64 79 s:Header><s:Body
0210: 2F 3E 3C 2F 73 3A 45 6E - 76 65 6C 6F 70 65 3E /></s:Envelope>

[10/31/07 10:27:59:658 IST] 0000001e WebServicesSe E com.ibm.ws.webservices.engine.transport.http.WebServicesServlet getSoapAction WSWS3112E: Error: Generating WebServicesFault due to missing SOAPAction.
WebServicesFault
faultCode: Client.NoSOAPAction
faultString: WSWS3147E: Error: no SOAPAction header!
faultActor: null
faultDetail:

can any body help me..please
thanks
swarna

This is from the client request:



xmlns:s="http://www.w3.org/2003/05/soap-envelope" identifies this as a SOAP 1.2 envelope.

From your WSDL:


The WSDL is specifying the use of SOAP 1.1 ("http://schemas.xmlsoap.org/soap/envelope/")

In SOAP 1.2 the SOAPAction HTTP-header was replaced with the (optional) action attribute on the application/soap+xml media type
A.3 The action Parameter

Also the the SOAPAction specified in your WSDL is not a URI which it should be, something like "http://ejb.test.hp/actions/postOrder". It doesn't have to be addressable but it has to follow the rules of a URI.
However with SOAP 1.2 that would still result in


not in

as required under SOAP 1.1.

Change the SOAPAction in your WSDL to a URI.

Force the .NET client to generate SOAP 1.1 requests, not SOAP 1.2 requests.

Hi
Thank you very much for the reply.
i will check the mentioned steps..


swarna

Hii
i checked the first condition
1)Change the SOAPAction in your WSDL to a URI.
this one was done.but still i am getting the error.

2)Force the .NET client to generate SOAP 1.1 requests, not SOAP 1.2 requests.

Here how can i change the SOAP1.2 request to SOAP1.1 request.
Can you please guide me.

thank you
swarna

It seems that the .NET wsdl.exe generates a SOAP 1.1 proxy with a command option of /protocol:SOAP and a SOAP 1.2 proxy with /protocol:SOAP12.

On the client side you can also configure the proxy programmatically to select SOAP 1.1 or 1.2 by setting the SoapVersion property of the proxy class.

SoapProtocolVersion Enumeration

I am not able to get proxy.soapversion.its showing System.Web.Services.Protocols is not available.
I have to add any more in config file?
Please let me know.

swarna.

Well - you have a bit of a mystery on your hands. The .NET Framework 1.1 didn't support SOAP 1.2 and the .NET Framework 2.0 introduced System.Web.Services.Protocols.SoapProtocolVersion which can be found in the system.web.services.dll assembly.