I added two filters to help with content-encoding on the server side recently to SVN:
https://issues.apache.org/jira/browse/WINK-152 http://svn.apache.org/viewvc?view=revision&revision=951149 In WebSphere 6.1 and 7.0, inbound requests are automatically gzip decoded by default, so you should only need the filter for the outgoing response. If you want, you can grab the latest code or snapshot build and try the filters out. You should add: <filter> <filter-name>ContentEncodingResponseFilter</filter-name> <filter-class>org.apache.wink.server.internal.servlet.contentencode.ContentEncodingResponseFilter</filter-class> </filter> <filter-mapping> <filter-name>ContentEncodingResponseFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> to your web.xml. You can also make your own custom filter and try a similar approach to gzip encode your outgoing responses. On Tue, Jun 1, 2010 at 10:40 AM, srinivasan venkat <[email protected]> wrote: > I need to achieve HTTP request and response messages to contain compressed > data using Gzip in WebSphere container.=20 > In the WebSphere document they suggested to have, > Accept-Encoding: gzip > Content-Encoding: gzip > in the HTTP header in request and response. > http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp?topic=3D= > /com.ibm.bspace.620.help.api.rest.doc/apis/wsprocessserver/index.htm > In my code, > I need to achieve this condition while specifying path "/retrieve" which > will have multiple XML as input. > Is there any way how we can achieve this to achieve the Gzip in WebSphere > using the Wink methods. > Need help in this regard. > > >
