You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dr. Dietmar Wolz (JIRA)" <ji...@apache.org> on 2012/06/27 15:35:42 UTC
[jira] [Created] (CXF-4397) Cached Reader/Writer in
org.apache.cxf.io
Dr. Dietmar Wolz created CXF-4397:
-------------------------------------
Summary: 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
Fix For: 2.6.2
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4397) Cached Reader/Writer in
org.apache.cxf.io
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-4397:
-----------------------------
Fix Version/s: (was: 2.6.2)
> 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
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4397) Cached Reader/Writer in
org.apache.cxf.io
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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