Hey DreamRyder,

THANKS A TONNNNN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This does solve the problem, you are great man!!!!....I was crying my heart
out on this problem.


Thanks and regards,
Pushkar



dreamryder wrote:
> 
> The "d4" and "0" thing are caused by chunking turned on by default, in
> Axis, I believe.
> Turn it off and those extraneous characters will go away.
> http://wso2.org/library/952
> Suspect .NET doesn't have chunking, or at least doesn't have it on by
> default.
> -jeff
> 
> 
> -----Original Message-----
> From: Pushkar Bodas [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 16, 2007 2:51 PM
> To: axis-user@ws.apache.org
> Subject: Re: Consuming .NET exposed web service by an Axis2 ADB Client
> gives Error 400 : Bad Request
> 
> 
> Hi,
> 
> I know I have been posting a lot of replies myself, but any small thing
> that
> I notice, I just put it here just to see if I can get any kind of help.
> This
> is what I have discovered right now :
> 
> I was playing around with the TCPMon tool and discovered that if we
> remove
> the "d4" and "0" from the request and add the parameter of
> "Content-Length"
> to the header, the server responds correctly. 
> 
> So I am going ahead with this lead right now and in case any one of you
> can
> help me do these, please let me know.
> 
> Thanks and regards,
> Pushkar
> 
> 
> 
> Ajith Ranabahu wrote:
>> 
>> Hi,
>> By a casual look this seems to be a SOAP version problem. I see the
>> SOAPAction header in the C# client and not in the Axis2 client.
>> SOAPAction header is a specific header that is required in SOAP 1.1
>> and the reason why the server coughs could be that
>> 
>> Ajith
>> 
>> On 8/15/07, Pushkar Bodas <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> I used the tcpmon utility and I have posted the messages accordingly.
> I
>>> forgot to mention 1 more thing : the "Sender" utility of tcpmon if
> used
>>> to
>>> send the soap request alone, works fine with the .NET server too. So
> I
>>> think
>>> there is a problem either with the soap header part, where we see the
>>> elements "Content-Type","User-Agent" etc, or another problem could be
> the
>>> "d2" and "0" thing wrapping the soap message. Please help.
>>>
>>> Thanks and regards,
>>> Pushkar
>>>
>>>
>>>
>>> Pushkar Bodas wrote:
>>> >
>>> > Hi,
>>> >
>>> > Thanks for this utility. Its just awesomeee!!!..... I have the soap
>>> > envolopes that my 2 clients send to the .NET server.
>>> >
>>> > /////////////////////////////////////////////
>>> > AXIS2 client soap request looks like :
>>> > /////////////////////////////////////////////
>>> >
>>> >
>>> > POST /NetWebService/Service.asmx HTTP/1.1
>>> > Content-Type: application/soap+xml; charset=UTF-8;
>>> > action="http://tempuri.org/HelloWorld";
>>> > User-Agent: Axis2
>>> > Host: localhost:8888
>>> > Transfer-Encoding: chunked
>>> >
>>> > d2
>>> > <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
>>> >
>>>
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Body><n
> s1:HelloWorld
>>> > xmlns:ns1="http://tempuri.org/";
> /></soapenv:Body></soapenv:Envelope>
>>> > 0
>>> >
>>> > /////////////////////////////////////////////////////////
>>> > AND ITS RESPONSE FROM THE SERVER LOOKS LIKE
>>> > /////////////////////////////////////////////////////////
>>> >
>>> > HTTP/1.1 400 Bad Request
>>> > Server: ASP.NET Development Server/8.0.0.0
>>> > Date: Wed, 15 Aug 2007 18:17:34 GMT
>>> > X-AspNet-Version: 2.0.50727
>>> > Cache-Control: private
>>> > Content-Length: 0
>>> > Connection: Close
>>> >
>>> > //////////////////////////////////////////////////////////
>>> > C# CLIENT REQUEST LOOKS LIKE
>>> > ////////////////////////////////////////////////////////
>>> > POST /NetWebService/Service.asmx HTTP/1.1
>>> > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services
> Client
>>> > Protocol 2.0.50727.832)
>>> > VsDebuggerCausalityData:
>>> >
>>>
> uIDPox4NuUliSldAjIMgGG2urLgAAAAAkLdSv8ASc0u3Kfpo5fVQ2wgvwH3CSjZMmjOwRx4k
> fx4ACAAA
>>> > Content-Type: text/xml; charset=utf-8
>>> > SOAPAction: "http://tempuri.org/HelloWorld";
>>> > Host: localhost:8889
>>> > Content-Length: 288
>>> > Expect: 100-continue
>>> > Connection: Keep-Alive
>>> >
>>> > <?xml version="1.0" encoding="utf-8"?><soap:Envelope
>>> > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
>>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";><soap:Body><HelloWorld
>>> > xmlns="http://tempuri.org/"; /></soap:Body></soap:Envelope>
>>> >
>>> > //////////////////////////////////////////////////////////
>>> > AND ITS RESPONSE LOOKS LIKE
>>> > ///////////////////////////////////////////////////////////
>>> > HTTP/1.1 100 Continue
>>> > Server: ASP.NET Development Server/8.0.0.0
>>> > Date: Wed, 15 Aug 2007 18:09:25 GMT
>>> > Content-Length: 0
>>> >
>>> > HTTP/1.1 200 OK
>>> > Server: ASP.NET Development Server/8.0.0.0
>>> > Date: Wed, 15 Aug 2007 18:09:25 GMT
>>> > X-AspNet-Version: 2.0.50727
>>> > Cache-Control: private, max-age=0
>>> > Content-Type: text/xml; charset=utf-8
>>> > Content-Length: 374
>>> > Connection: Close
>>> >
>>> > ////////////////////////////////////////
>>> > END
>>> > ///////////////////////////////////////
>>> >
>>> > I havent still got it as to why it isnt working. Im looking into it
>>> > now....as now I atleast have a lead. If you can tell from this what
> the
>>> > problem is, I would highly appreciate the help.
>>> >
>>> > Thanks and regards,
>>> > Pushkar
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > Amila Suriarachchi wrote:
>>> >>
>>> >> can you use the tcp mon[1]  and check the reqest send from the
> axis2
>>> >> client
>>> >> and
>>> >> response it gets.
>>> >>
>>> >> [1]http://ws.apache.org/commons/tcpmon/
>>> >>
>>> >> Amila.
>>> >>
>>> >>
>>> >> On 8/15/07, Pushkar Bodas <[EMAIL PROTECTED]> wrote:
>>> >>>
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> Thanks for the reply.
>>> >>>
>>> >>> I guess I have used the correct EPR. This is the same EPR that I
> am
>>> >>> using
>>> >>> in
>>> >>> the C# client.
>>> >>> The EPR looks something like :
>>> >>> "http://localhost:2489/WebServiceName/Service.asmx";. This is what
> I
>>> use
>>> >>> in
>>> >>> the C# client and in the axis client too. I hope this is correct.
>>> >>>
>>> >>> The problem still remains, so any other suggestions regarding
> what
>>> may
>>> >>> be
>>> >>> wrong?
>>> >>>
>>> >>> Thanks and regards,
>>> >>> Pushkar
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> Amila Suriarachchi wrote:
>>> >>> >
>>> >>> > This is a problem with your epr (end point reference).
>>> >>> >
>>> >>> > When generating the stubs with the wsdl2java tool, it writes
> the
>>> epr
>>> >>> > specified in the Port element (in the wsdl) to the stub file.
> Then
>>> if
>>> >>> you
>>> >>> > do
>>> >>> > not override this (by giving the epr to stub) it uses this
> already
>>> >>> saved
>>> >>> > epr.
>>> >>> >
>>> >>> > Please check this epr is correct or not.
>>> >>> >
>>> >>> > Amila.
>>> >>> >
>>> >>> > On 8/15/07, Pushkar Bodas <[EMAIL PROTECTED]> wrote:
>>> >>> >>
>>> >>> >>
>>> >>> >> Hi,
>>> >>> >>
>>> >>> >> I am a newbie to AXIS2 and .NET too. I exposed a web service
> in
>>> .NET
>>> >>> and
>>> >>> >> I
>>> >>> >> am trying to consume it by using AXIS2's ADB client. The way
> in
>>> which
>>> >>> >> .NET
>>> >>> >> creates the WSDL makes the WSDL2java utility of AXIS2 to
> generate
>>> >>> request
>>> >>> >> classes for even those web-methods, which do not take any
>>> parameters.
>>> >>> >> Hence
>>> >>> >> the scenario is that all the methods to be used, have to be
> passed
>>> an
>>> >>> >> object
>>> >>> >> whenever I have to use the Stub.Method(Object).
>>> >>> >>
>>> >>> >> When I do this, everything seems to go on fine, inclusing the
>>> >>> creation
>>> >>> of
>>> >>> >> the SOAP Envolope too. But the OperationClient.execute(true)
>>> method
>>> >>> in
>>> >>> >> the
>>> >>> >> Stub class throws an exception as the one shown below :
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> >>> >> ////////////////////
>>> >>> >> EXCEPTION
>>> >>> >> ///////////////////
>>> >>> >>
>>> >>> >>
>>> >>> >> org.apache.axis2.AxisFault: Transport error: 400 Error: Bad
>>> Request
>>> >>> >>         at
>>> >>> >>
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
>>> >>> >> CommonsHTTPTransportSender.java:221)
>>> >>> >>         at
>>> >>> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:452)
>>> >>> >>         at
>>> >>> >> org.apache.axis2.description.OutInAxisOperationClient.send(
>>> >>> >> OutInAxisOperation.java:330)
>>> >>> >>         at
>>> >>> >> org.apache.axis2.description.OutInAxisOperationClient.execute(
>>> >>> >> OutInAxisOperation.java:294)
>>> >>> >>         at
>>> >>> >> org.tempuri.ServiceServiceSoap12Stub.ReverseString(
>>> >>> >> ServiceServiceSoap12Stub.java:409)
>>> >>> >>         at org.tempuri.Main.main(Main.java:30)
>>> >>> >> Caused by: org.apache.axis2.AxisFault: Transport error: 400
> Error:
>>> >>> Bad
>>> >>> >> Request
>>> >>> >>         at
>>> >>> >>
>>> >>> >>
>>> >>>
>>>
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
> ithCommons
>>> >>> >> (CommonsHTTPTransportSender.java:314)
>>> >>> >>         at
>>> >>> >>
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
>>> >>> >> CommonsHTTPTransportSender.java:201)
>>> >>> >>         ... 5 more
>>> >>> >> Caused by: org.apache.axis2.AxisFault: Transport error: 400
> Error:
>>> >>> Bad
>>> >>> >> Request
>>> >>> >>         at
>>> >>> >>
>>> >>>
>>>
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java
>>> >>> >> :179)
>>> >>> >>         at
>>> >>> >>
> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java
>>> >>> >> :73)
>>> >>> >>         at
>>> >>> >>
>>> >>> >>
>>> >>>
>>>
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW
> ithCommons
>>> >>> >> (CommonsHTTPTransportSender.java:305)
>>> >>> >>         ... 6 more
>>> >>> >> Caused by: org.apache.axis2.AxisFault: Transport error: 400
> Error:
>>> >>> Bad
>>> >>> >> Request
>>> >>> >>         at
>>> >>> >> org.apache.axis2.transport.http.HTTPSender.handleResponse(
>>> >>> HTTPSender.java
>>> >>> >> :320)
>>> >>> >>         at
>>> >>> >>
>>> >>>
>>>
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java
>>> >>> >> :177)
>>> >>> >>         ... 8 more
>>> >>> >>
>>> >>> >>
>>> >>> >> /////////////////////////
>>> >>> >> END OF EXCEPTION
>>> >>> >> /////////////////////////
>>> >>> >>
>>> >>> >> I used the WSDL2java utility to create the Stub from the web
>>> service
>>> >>> >> exposed
>>> >>> >> by .NET. The exposed webservice works fine as I have tested it
>>> with a
>>> >>> >> client
>>> >>> >> in C#.
>>> >>> >>
>>> >>> >> Can someone please help me with this?...I am stuck over here
> for a
>>> >>> couple
>>> >>> >> of
>>> >>> >> days. This can be quite a silly question, but since I am new
> to
>>> >>> AXIS2,
>>> >>> I
>>> >>> >> do
>>> >>> >> not know how to resolve this problem. Thanks in advance.
>>> >>> >>
>>> >>> >> Thanks and regards,
>>> >>> >> Pushkar
>>> >>> >>
>>> >>> >> --
>>> >>> >> View this message in context:
>>> >>> >>
>>> >>>
>>>
> http://www.nabble.com/Consuming-.NET-exposed-web-service-by-an-Axis2-ADB
> -Client-gives-Error-400-%3A-Bad-Request-tf4269311.html#a12150977
>>> >>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>>> >>> >>
>>> >>> >>
>>> >>> >>
>>> ---------------------------------------------------------------------
>>> >>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> >>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>>> >>> >>
>>> >>> >>
>>> >>> >
>>> >>> >
>>> >>> > --
>>> >>> > Amila Suriarachchi,
>>> >>> > WSO2 Inc.
>>> >>> >
>>> >>> >
>>> >>>
>>> >>> --
>>> >>> View this message in context:
>>> >>>
>>>
> http://www.nabble.com/Consuming-.NET-exposed-web-service-by-an-Axis2-ADB
> -Client-gives-Error-400-%3A-Bad-Request-tf4269311.html#a12161029
>>> >>> Sent from the Axis - User mailing list archive at Nabble.com.
>>> >>>
>>> >>>
>>> >>>
> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> >>> For additional commands, e-mail: [EMAIL PROTECTED]
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi,
>>> >> WSO2 Inc.
>>> >>
>>> >>
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>>
> http://www.nabble.com/Consuming-.NET-exposed-web-service-by-an-Axis2-ADB
> -Client-gives-Error-400-%3A-Bad-Request-tf4269311.html#a12171573
>>> Sent from the Axis - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>> 
>> 
>> -- 
>> Ajith Ranabahu
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Consuming-.NET-exposed-web-service-by-an-Axis2-ADB
> -Client-gives-Error-400-%3A-Bad-Request-tf4269311.html#a12187222
> Sent from the Axis - User mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Consuming-.NET-exposed-web-service-by-an-Axis2-ADB-Client-gives-Error-400-%3A-Bad-Request-tf4269311.html#a12189722
Sent from the Axis - User mailing list archive at Nabble.com.


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

Reply via email to