You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2010/11/24 07:46:13 UTC

[jira] Resolved: (CXF-3146) make gzip encoding works over jms transport

     [ https://issues.apache.org/jira/browse/CXF-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved CXF-3146.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.4)
                       (was: 2.3.1)

commit fix
http://svn.apache.org/viewvc?rev=1038498&view=rev for 2.2 branch

> make gzip encoding works over jms transport
> -------------------------------------------
>
>                 Key: CXF-3146
>                 URL: https://issues.apache.org/jira/browse/CXF-3146
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.2.12
>
>         Attachments: CXF-3146.patch
>
>
> seems currently gzip content-encoding only works with http transport, all gzip related interceptors are in cxf-rt-transport-http module, but IMHO gzip content-encoding should be decoupled with the underlying transport. From my initial investigation, support gzip content-encoding over jms transport is doable if jms client use binary message mode, we only need address some protocol header mismatch issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.