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

["Freeman Fang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934808#action_12934808 ] 

Freeman Fang commented on CXF-3146:
-----------------------------------

This patch only works with 2.2.x branch.

Since cxf 2.3, cxf implements the soap over jms spec which ensure interoperability between the implementations of different Web services vendors, in the  soap over jms spec [1], there's no headers like Content-Encoding/Accept-Encoding defined which is mandatory for gzip support, so I think we can't make gzip encoding works after cxf 2.3 along with soap over jms spec. 

So  we can only support gzip over jms on cxf 2.2.x branch.
[1]http://cxf.apache.org/docs/soap-over-jms-10-support.html

> 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, 2.3.1, 2.4
>
>         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.