[
https://issues.apache.org/jira/browse/AXIS2-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496289
]
Toni Alatalo commented on AXIS2-2657:
-------------------------------------
and mine respectively. the reply from IIS seems to be as expected otherwise,
but there is a HTTP/1.1 100 Continue block before the actual response. i do not
know what those '1ee' and '0' before and after the request are, in another
request they are '237' and '0'. with the python ZSI tool i did not get this
behaviour and was hence able to prototype (there it seems that not all
functions work though, might be incompleteness of the implementation, don't
know).
POST /CirixWebService/CirixWebService.asmx HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8;
action="http://atexuri.fi/GetNextInvno";
User-Agent: Axis2
Host: localhost:9995
Transfer-Encoding: chunked
1ee
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Header><wsa:To>http://localhost:9995/CirixWebService/CirixWebService.asmx</wsa:To><wsa:MessageID>urn:uuid:CA78D3A88AAFFD0E1C1179320930689</wsa:MessageID><wsa:Action>http://atexuri.fi/GetNextInvno</wsa:Action></soapenv:Header><soapenv:Body><ns1:GetNextInvno
xmlns:ns1="http://atexuri.fi/"; /></soapenv:Body></soapenv:Envelope>
0
> Addressing Issue :Header
> http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate
> recipient is required but not present in the message.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2657
> URL: https://issues.apache.org/jira/browse/AXIS2-2657
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api, kernel, transports, wsdl
> Affects Versions: 1.2
> Environment: Windows XP Devlopment : Eclips 3.2.1 Cleint Side Axis2
> 1.2 Generation
> Server:: Remote Server written in WSE 3.0 Microsoft Technology
> Reporter: Shweta Desai
> Priority: Blocker
> Fix For: 1.2
>
>
> Hi,
> I am trying to connect to the server which has been written in WES 3.0, SOAP
> 1.2/1.1 bindings.
> Generated Stubs are in xmlBean for Soap 1.2/1.1. This is synchronous
> communication.
> Error :
> May 11, 2007 12:43:28 PM org.apache.commons.httpclient.HttpMethodBase
> readResponse
> INFO: Discarding unexpected response: HTTP/1.1 100 Continue
> org.apache.axis2.AxisFault: Header
> http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate
> recipient is required but not present in the message.
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
> at
> gov.ca.edd.FsetServiceFsetServiceSoapStub.SendTransmission(FsetServiceFsetServiceSoapStub.java:843)
> at com.adp.ca.efiling.CATestWebServices.main(CATestWebServices.java:339)
> Code :
> I have already set the below property.
> But still getting the error.
> ConfigurationContext c =
> ConfigurationContextFactory.createEmptyConfigurationContext();
> c.setProperty("WSAddressingVersion",
> "http://schemas.xmlsoap.org/ws/2004/08/addressing";);
> ClientSoapStub edd = new ClientSoapStub
> (c,"https://fsettestprod.edd.ca.gov/fsetproxy/fsetservice.asmx";);
> ServiceClient serviceclient=edd._getServiceClient();
> Options o =serviceclient.getOptions();
> o.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);
> TransportOutDescription tod = new
> TransportOutDescription(org.apache.axis2.Constants.TRANSPORT_HTTP);
> CommonsHTTPTransportSender httpSender = new CommonsHTTPTransportSender();
> tod.setSender(httpSender);
> o.setTransportOut(tod);
> Your input is appreciated. I am stuck with this error for one week now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
