cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-4397) Cached Reader/Writer in org.apache.cxf.io
Date Thu, 27 Sep 2012 21:47:08 GMT

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

Daniel Kulp resolved CXF-4397.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.0
         Assignee: Daniel Kulp
    
> Cached Reader/Writer in org.apache.cxf.io
> -----------------------------------------
>
>                 Key: CXF-4397
>                 URL: https://issues.apache.org/jira/browse/CXF-4397
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.6.1
>            Reporter: Dr. Dietmar Wolz
>            Assignee: Daniel Kulp
>             Fix For: 2.7.0
>
>
> In version 2.6 support of Readers/Writers attached to the message representing the content
were added. Implementation of SAM for Talend ESB needed to be adapted in case JMS is used
as transport. The current fix converts attached Readers/Writers to streams in SAM using UTF-8
encoding. It works but I am not sure this is consistent with what was indended by supporting
Readers/Writers in CXF. To defer encoding also in case monitoring is enabled I would prefer
to use cached Readers/Writers instead converting into streams thereby fixing the encoding.
Proper place for cached Reader/Writer would be org.apache.cxf.io, where the already existing
cached streams are located.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message