Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5113

Message trace modifies character encoding

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jboss-fuse-6.0, jboss-fuse-6.3
    • Fix Version/s: jboss-fuse-6.3
    • Component/s: SwitchYard
    • Labels:
      None
    • Environment:

      Fuse Service Works 6.0

    • Sprint:
      6.3 Sprint 4 (Mar 28 - Apr 29)
    • Steps to Reproduce:
      Hide

      Deploy the attached application to FSW 6. Inside the application, modify the META-INF/switchyard.xml file to point to a directory on your local system:
      <file:binding.file name="file1">
      <file:contextMapper includes=".*"/>
      <file:directory>/Users/dboeren/tinput</file:directory>
      <file:charset>ISO-8859-15</file:charset>
      <file:consume/>
      </file:binding.file>

      Turn on message trace (org.switchyard.handlers.messageTrace.enabled=true) and copy the attached ISO-8859-15.xml file into the watched directory to trigger the test. With message trace on, the character encoding is modified. With message trace off, it is not. Look at the "nachname" field in the XML for a good example, with correct charset encoding it should look like this:
      <tns:nachname>äßHödl</tns:nachname>

      mweiler had a proposed fix but it does not seem to solve the issue. I am attaching it for reference as it may provide a good starting point.

      Show
      Deploy the attached application to FSW 6. Inside the application, modify the META-INF/switchyard.xml file to point to a directory on your local system: < file:binding.file name="file1"> < file:contextMapper includes=".*"/> < file:directory >/Users/dboeren/tinput</ file:directory > < file:charset >ISO-8859-15</ file:charset > < file:consume/ > </ file:binding.file > Turn on message trace (org.switchyard.handlers.messageTrace.enabled=true) and copy the attached ISO-8859-15.xml file into the watched directory to trigger the test. With message trace on, the character encoding is modified. With message trace off, it is not. Look at the "nachname" field in the XML for a good example, with correct charset encoding it should look like this: <tns:nachname>äßHödl</tns:nachname> mweiler had a proposed fix but it does not seem to solve the issue. I am attaching it for reference as it may provide a good starting point.

      Description

      Enabling message trace (org.switchyard.handlers.messageTrace.enabled=true) causes the character encoding of the message to be modified.

        Gliffy Diagrams

          Attachments

          1. eap630067_error.log
            29 kB
          2. encoding.patch
            2 kB
          3. fileencoding-0.0.1-SNAPSHOT.jar.zip
            14 kB
          4. ISO-8859-15.xml
            5 kB

            Issue Links

              Activity

                People

                • Assignee:
                  tcunning Thomas Cunningham
                  Reporter:
                  david.boeren David Boeren
                  Tester:
                  Stefan Veres
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: