Hi, I tested this with the latest code and it does work. Make sure you use the new build on the client side and that the axis2-transports jar is in the classpath (The fix was actually done in the transports project). You can even try taking a checkout of the transports project [1] and building it your self.
Thais is how my response looked, HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Encoding: identity Content-Type: application/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Sat, 04 Oct 2008 04:41:31 GMT 5c <ns:echoResponse xmlns:ns="http://ws.apache.org/axis2"> <return>hi</return></ns:echoResponse> 0 Axis2 was able to accept this response after the change. Thanks, Keith. [1] https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport On Fri, Oct 3, 2008 at 8:47 PM, <[EMAIL PROTECTED]> wrote: > here is the stace trace for the error > > org.apache.axis2.AxisFault: HTTP :unsupported content-encoding of > 'identity' found > > at org.apache.axis2.transport.http.AbstractHTTPSender.processResponse( > *AbstractHTTPSender.java:224*) > > at org.apache.axis2.transport.http.HTTPSender.handleResponse( > *HTTPSender.java:265*) > > at org.apache.axis2.transport.http.HTTPSender.sendViaPost( > *HTTPSender.java:190*) > > at org.apache.axis2.transport.http.HTTPSender.send( > *HTTPSender.java:75*) > > at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons( > *CommonsHTTPTransportSender.java:370*) > > at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke( > *CommonsHTTPTransportSender.java:209*) > > > > > > > > at org.apache.axis2.engine.AxisEngine.send( > *AxisEngine.java:432*) > > at org.apache.axis2.description.OutInAxisOperationClient.send( > *OutInAxisOperation.java:401*) > > at org.apache.axis2.description.OutInAxisOperationClient.executeImpl( > *OutInAxisOperation.java:228*) > > at org.apache.axis2.client.OperationClient.execute( > *OperationClient.java:163* > ) > > at com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.extract( > *OrderStatusServiceStub.java:816*) > > at ClientCDAS.multipleParameters( > *ClientCDAS.java:36*) > > at ClientCDAS.main( > *ClientCDAS.java:14*) > > > *Sangita Pandit* > *728 1606* > > > ------------------------------ > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *Sent:* Friday, October 03, 2008 10:08 AM > *To:* axis-user@ws.apache.org > *Subject:* RE: Error "HTTP :unsupported content-encoding of 'identity' > found" > > I fetched the nightly build today and tried it out to see if the > exception has been resolved. However, I still see the same error. One > thing to note is that the build logs for the nightly build had some test > failures. Please can you let me know if the changes you did for solving > this issue are in the nightly build. > > > *Sangita Pandit* > *728 1606* > > > ------------------------------ > *From:* keith chapman [mailto:[EMAIL PROTECTED] > *Sent:* Thursday, October 02, 2008 10:51 PM > *To:* axis-user@ws.apache.org > *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity' > found" > > We run the Axis2 nightly build at WSO2 <http://wso2.com> as well. So you > should be able to get it off the builder machine > here<http://builder.wso2.org/browse/AXIS2-NIGHTLY/latest/artifact>[1] > > Thanks, > Keith. > > [1] http://builder.wso2.org/browse/AXIS2-NIGHTLY/latest/artifact > > On Fri, Oct 3, 2008 at 8:52 AM, <[EMAIL PROTECTED]> wrote: > >> what is the location of the nightly builds. I am getting access >> forbidden when I try to access >> http://ws.zones.apache.org/dist/axis2/nightly/ >> >> >> *Sangita Pandit* >> *728 1606* >> >> >> ------------------------------ >> *From:* keith chapman [mailto:[EMAIL PROTECTED] >> *Sent:* Tuesday, September 30, 2008 8:04 PM >> >> *To:* axis-user@ws.apache.org >> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity' >> found" >> >> We do not have a Axis2 release planned for any time soon. So you may >> have to get the nightly. >> >> Thanks, >> Keith. >> >> On Wed, Oct 1, 2008 at 1:33 AM, <[EMAIL PROTECTED]> wrote: >> >>> How can I get the jar and when will this change be in the official >>> release. >>> >>> >>> *Sangita Pandit* >>> *728 1606* >>> >>> >>> ------------------------------ >>> *From:* keith chapman [mailto:[EMAIL PROTECTED] >>> *Sent:* Tuesday, September 30, 2008 12:31 PM >>> >>> *To:* axis-user@ws.apache.org >>> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity' >>> found" >>> >>> I have fixed this in the transports module. >>> >>> Thanks, >>> Keith. >>> >>> On Tue, Sep 30, 2008 at 7:57 PM, <[EMAIL PROTECTED]> wrote: >>> >>>> Also to be backwards compatible, AXIS2 has to support it as the AXIS >>>> did not have issues like this. >>>> >>>> >>>> *Sangita Pandit* >>>> *728 1606* >>>> >>>> >>>> ------------------------------ >>>> *From:* keith chapman [mailto:[EMAIL PROTECTED] >>>> *Sent:* Tuesday, September 30, 2008 4:20 AM >>>> *To:* axis-user@ws.apache.org >>>> *Subject:* Re: Error "HTTP :unsupported content-encoding of 'identity' >>>> found" >>>> >>>> On Tue, Sep 30, 2008 at 2:40 PM, Andreas Veithen < >>>> [EMAIL PROTECTED]> wrote: >>>> >>>>> Googling for "Content-encoding: identity" reveals that this is actually >>>>> quite common, so I guess that we should indeed support it. >>>> >>>> >>>> Exactly. And we wont have to do much jsut ignore the content-type if its >>>> identity. >>>> >>>> Thanks, >>>> Keith . >>>> >>>>> >>>>> >>>>> Andreas >>>>> >>>>> keith chapman wrote: >>>>> >>>>>> Interesting, It says SHOULD NOT but not MUST NOT. So it may be >>>>>> acceptable to have this header too. I guess one could argue that Axis2 >>>>>> should ignore it if there is a header which says Content-encoding: >>>>>> identity. >>>>>> WDYT? >>>>>> >>>>>> Thanks, >>>>>> Keith. >>>>>> >>>>>> On Tue, Sep 30, 2008 at 12:01 AM, Andreas Veithen < >>>>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: >>>>>> >>>>>> RFC2616, section 3.5 says the following about the identity content >>>>>> encoding: "This content-coding is used only in the Accept-Encoding >>>>>> header, and SHOULD NOT be used in the Content-Encoding header." >>>>>> Assuming that the error is triggered by the Content-Encoding >>>>>> header, the behavior of Axis2 in this particular case seems to be >>>>>> acceptable. >>>>>> >>>>>> Andreas >>>>>> >>>>>> >>>>>> On 29 sept. 08, at 19:23, keith chapman wrote: >>>>>> >>>>>> I just had a look at the code and it looks like we dont deal >>>>>> with identity content encoding (whereas we should). Could you >>>>>> use TCPMonitor to trace to request and response please. If you >>>>>> want to use the TCPMonitor plugin this how to [1] would help. >>>>>> >>>>>> Thanks, >>>>>> Keith. >>>>>> >>>>>> [1] >>>>>> >>>>>> http://www.keith-chapman.org/2008/07/using-tcp-monitor-to-debug-web-service.html >>>>>> >>>>>> On Mon, Sep 29, 2008 at 10:19 PM, <[EMAIL PROTECTED] >>>>>> <mailto:[EMAIL PROTECTED]>> wrote: >>>>>> I generated the stubs using the WSDLToJava tool. >>>>>> >>>>>> Sangita Pandit >>>>>> 728 1606 >>>>>> >>>>>> >>>>>> >>>>>> From: keith chapman [mailto:[EMAIL PROTECTED] >>>>>> <mailto:[EMAIL PROTECTED]>] >>>>>> Sent: Monday, September 29, 2008 11:47 AM >>>>>> To: axis-user@ws.apache.org <mailto:axis-user@ws.apache.org> >>>>>> Subject: Re: Error "HTTP :unsupported content-encoding of >>>>>> 'identity' found" >>>>>> >>>>>> Hi, >>>>>> >>>>>> How did you write the client for this service? Did you use >>>>>> ServiceClient API or did you use a generated stub? >>>>>> >>>>>> Thanks, >>>>>> Keith. >>>>>> >>>>>> On Mon, Sep 29, 2008 at 8:26 PM, <[EMAIL PROTECTED] >>>>>> <mailto:[EMAIL PROTECTED]>> wrote: >>>>>> I am getting this error when webservice client is trying to >>>>>> make a call to the webservice method. I am using the released >>>>>> version of Axis2 1.4.1. <http://1.4.1.> >>>>>> >>>>>> >>>>>> See stack trace here >>>>>> org.apache.axis2.AxisFault: HTTP :unsupported content-encoding >>>>>> of 'identity' found >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:223) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:265) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190) >>>>>> at >>>>>> >>>>>> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371) >>>>>> >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209) >>>>>> at >>>>>> org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228) >>>>>> at >>>>>> >>>>>> >>>>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) >>>>>> at >>>>>> >>>>>> >>>>>> com.dell.gmfs.backlog.cdas.OrderStatusServiceStub.Extract(OrderStatusServiceStub.java:1056) >>>>>> at >>>>>> >>>>>> >>>>>> com.dell.gmfs.backlog.cdas.OrderStatusServiceTest.testExtract(OrderStatusServiceTest.java:37) >>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>>>> Method) >>>>>> at >>>>>> >>>>>> >>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>>> at >>>>>> >>>>>> >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> at java.lang.reflect.Method.invoke(Method.java:585) >>>>>> at junit.framework.TestCase.runTest(TestCase.java:154) >>>>>> at junit.framework.TestCase.runBare(TestCase.java:127) >>>>>> at >>>>>> junit.framework.TestResult$1.protect(TestResult.java:106) >>>>>> at >>>>>> junit.framework.TestResult.runProtected(TestResult.java:124) >>>>>> at junit.framework.TestResult.run(TestResult.java:109) >>>>>> at junit.framework.TestCase.run(TestCase.java:118) >>>>>> at junit.framework.TestSuite.runTest(TestSuite.java:208) >>>>>> at junit.framework.TestSuite.run(TestSuite.java:203) >>>>>> at >>>>>> >>>>>> >>>>>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) >>>>>> at >>>>>> >>>>>> >>>>>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) >>>>>> >>>>>> Please advise what I am doing wrong. >>>>>> >>>>>> I have tried both XMLbean and databinding approach to generate >>>>>> the client code. >>>>>> >>>>>> Thanks >>>>>> Sangita Pandit >>>>>> 728 1606 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- Keith Chapman >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. >>>>>> Oxygenating the Web Service Platform. >>>>>> http://wso2.org/ >>>>>> >>>>>> blog: http://www.keith-chapman.org >>>>>> >>>>>> >>>>>> >>>>>> -- Keith Chapman >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. >>>>>> Oxygenating the Web Service Platform. >>>>>> http://wso2.org/ >>>>>> >>>>>> blog: http://www.keith-chapman.org >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>> <mailto:[EMAIL PROTECTED]> >>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>> <mailto:[EMAIL PROTECTED]> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Keith Chapman >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. >>>>>> Oxygenating the Web Service Platform. >>>>>> http://wso2.org/ >>>>>> >>>>>> blog: http://www.keith-chapman.org >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>> >>>> >>>> -- >>>> Keith Chapman >>>> Senior Software Engineer >>>> WSO2 Inc. >>>> Oxygenating the Web Service Platform. >>>> http://wso2.org/ >>>> >>>> blog: http://www.keith-chapman.org >>>> >>> >>> >>> >>> -- >>> Keith Chapman >>> Senior Software Engineer >>> WSO2 Inc. >>> Oxygenating the Web Service Platform. >>> http://wso2.org/ >>> >>> blog: http://www.keith-chapman.org >>> >> >> >> >> -- >> Keith Chapman >> Senior Software Engineer >> WSO2 Inc. >> Oxygenating the Web Service Platform. >> http://wso2.org/ >> >> blog: http://www.keith-chapman.org >> > > > > -- > Keith Chapman > Senior Software Engineer > WSO2 Inc. > Oxygenating the Web Service Platform. > http://wso2.org/ > > blog: http://www.keith-chapman.org > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org