CXF
  1. CXF
  2. CXF-4184

JMS transport w/ Text messages could stay as text

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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)

        Activity

        Daniel Kulp created issue -
        Daniel Kulp made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Daniel Kulp made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        22h 29m 1 Daniel Kulp 20/Mar/12 18:38
        Resolved Resolved Closed Closed
        33d 22h 7m 1 Daniel Kulp 23/Apr/12 17:45

          People

          • Assignee:
            Daniel Kulp
            Reporter:
            Daniel Kulp
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development