cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Created) (JIRA)" <>
Subject [jira] [Created] (CXF-4184) JMS transport w/ Text messages could stay as text
Date Mon, 19 Mar 2012 20:09:39 GMT
JMS transport w/ Text messages could stay as text

                 Key: CXF-4184
             Project: CXF
          Issue Type: Improvement
          Components: Transports
            Reporter: Daniel Kulp
            Assignee: Daniel Kulp
             Fix For: 2.6

When using TextMessage with JMS, CXF currently will convert the text back/forth into byte[]
to create Streams as much of the runtime expects Input/OutputStream.  It would be good if
the runtime could be updated to support Reader/Writer in addition to Input/OutputStream which
would allow the StringReader/Writer to avoid the extra levels of encoding and decoding. 

It's likely that not ALL of the runtime will be updatable easily.  In those cases, users should
still be able to use byte message.   (example, certain interceptors like the FastInfoset interceptors
that ONLY work with streams would not work with the TextMessage interactions, but they likely
would have resulting in wrong/bogus stuff previously anyway)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message