Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-346

UTF-8 problem with character: Č (resulting in question character)

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: 2.2.0.Final
    • Fix Version/s: 2.2.0.Final
    • Component/s: BPEL Deployer
    • Labels:
      None
    • Environment:

      jboss5.1, jbossesb4.9, riftsaw 2.2.0 on centos 5.2

    • Steps to Reproduce:
      Hide

      Make a default BPEL process and add an assign from input to output string. Deploy..

      If I call it with "write so čšž", it will respond with "write to ?šž". And the č character is used a lot...

      What is more... the characters from the ex-yugoslavian country like ć and đ doesn't work too

      Show
      Make a default BPEL process and add an assign from input to output string. Deploy.. If I call it with "write so čšž", it will respond with "write to ?šž". And the č character is used a lot... What is more... the characters from the ex-yugoslavian country like ć and đ doesn't work too

      Description

      Here is the code table for "Slovenian" special characters...

      UCS-2Dec UCS-2Hex UTF-8Hex HTML(&## UTF-8Native UnaccentedEnglish
      268 010C C4 8C Č Č C not supported
      269 010D C4 8D č č c not supported
      352 0160 C5 A0 Š Š S supported
      353 0161 C5 A1 š š s supported
      381 017D C5 BD Ž Ž Z supported
      382 017E C5 BE ž ž z supported

      Š and Ž working, Č is resulting in a question character.

      Log:
      2011-02-15 13:19:07,143 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl] (http-172.17.3.15-9000-5) Message content: <?xml version="1.0" encoding="UTF-8"?>
      <message><payload><cod:codesRequest xmlns:cod="http://kkissiskratel/codes">
      <cod:input>testiram čšž ČŠŽ</cod:input>
      </cod:codesRequest></payload></message>
      2011-02-15 13:19:07,144 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl] (http-172.17.3.15-9000-5) Commiting ODE MEX {MyRoleMex#hqejbhcnphr61a8w8i4pjt [Client hqejbhcnphr61a8w8i4pjs] calling

      {http://kkissiskratel/codes}

      codes.process(...)}
      2011-02-15 13:19:07,144 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl] (http-172.17.3.15-9000-5) Commiting transaction.
      2011-02-15 13:19:07,360 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.EndpointReferenceContextImpl] (ODEServer-67) Map access not implemented
      2011-02-15 13:19:07,361 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.MessageExchangeContextImpl] (ODEServer-67) Invoking a partner operation: showMessage
      2011-02-15 13:19:07,361 DEBUG [org.jboss.soa.bpel.runtime.engine.ode.MessageExchangeContextImpl] (ODEServer-67) Invoking a partner operation: showMessage
      2011-02-15 13:19:07,361 DEBUG [org.jboss.soa.bpel.runtime.ws.WebServiceClient] (ODEServer-67) Invoking dispatcher 2d6074c8-b446-40fc-bf51-677312b13e00
      2011-02-15 13:19:07,424 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-69) createElement

      {http://schemas.xmlsoap.org/soap/envelope/}

      env:Envelope
      2011-02-15 13:19:07,424 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-69) createElement

      {http://schemas.xmlsoap.org/soap/envelope/}

      env:Header
      2011-02-15 13:19:07,424 TRACE [org.jboss.wsf.common.DOMUtils] (ODEServer-69) createElement

      {http://schemas.xmlsoap.org/soap/envelope/}

      env:Body
      2011-02-15 13:19:07,427 DEBUG [org.jboss.soa.bpel.runtime.ws.WebServiceClient] (ODEServer-69) ODE outbound message:
      <message>
      <parameters>
      <showMessage xmlns='http://ws.apache.org/axis2'>
      <ns:args0 xmlns:ns='http://ws.apache.org/axis2'>testiram ?šž ?ŠŽ</ns:args0>
      </showMessage>
      </parameters>
      </message>

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                objectiser Gary Brown
                Reporter:
                izgur Igor JStarter
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: