Uploaded image for project: 'JBoss Enterprise Portal Platform'
  1. JBoss Enterprise Portal Platform
  2. JBEPP-1428

Unicode characters handling problem

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 5.2.0.CR03
    • Fix Version/s: 5.2.1.GA
    • Component/s: None
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      • Use the JSF Car Booking example from the portletbridge directory in the EPP bundle. Deploy it and start the server.
      • Put the application on a page and access it. Choose Spanish as the language in the first step.
      • Confirm all the steps until you get to the Customer Details form.
      • Choose Senor in the select (default value). Fill in Primer Nombre, Código postal and Numero de carta de crédito with some strings to avoid validation errors.
      • Submit the form.
      • If everything worked, you would be directed to the next page. This doesn't happen now because of the value in the select containing a "special" character (note: the other fields are fine since you don't see any error messages in the form).
      Show
      Use the JSF Car Booking example from the portletbridge directory in the EPP bundle. Deploy it and start the server. Put the application on a page and access it. Choose Spanish as the language in the first step. Confirm all the steps until you get to the Customer Details form. Choose Senor in the select (default value). Fill in Primer Nombre , Código postal and Numero de carta de crédito with some strings to avoid validation errors. Submit the form. If everything worked, you would be directed to the next page. This doesn't happen now because of the value in the select containing a "special" character (note: the other fields are fine since you don't see any error messages in the form).
    • Release Notes Text:
      Hide
      CAUSE

      HTTP Request parameters were retrieved before the character encoding was set to UTF-8

      CONSEQUENCE

      The default character encoding of ISO-8859-1 was used instead, leading to mangled characters

      FIX

      Set the character encoding to UTF-8 before Request parameters are accessed

      RESULT

      Correct unicode characters are returned in form posts
      Show
      CAUSE HTTP Request parameters were retrieved before the character encoding was set to UTF-8 CONSEQUENCE The default character encoding of ISO-8859-1 was used instead, leading to mangled characters FIX Set the character encoding to UTF-8 before Request parameters are accessed RESULT Correct unicode characters are returned in form posts
    • Release Notes Docs Status:
      Not Yet Documented
    • NEEDINFO:
      Nobody

      Description

      Scenario: I have a form in a JSF application. I submit the form with the fields containing Unicode characters and the validation fails even though the values are correct. I narrowed the problem down to Spanish characters getting messed up before the validation takes place.

      This is not an issue with EPP 5.1.1.GA and it must have been caused by a change in EPP, i.e. even though it is a JSF application used over Portlet Bridge, it looks like it's neither PBR nor an example problem - the same example with the same version of Portlet Bridge works fine on EPP 5.1.1 and doesn't work on EPP 5.2.0.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kenfinni Ken Finnigan
                  Reporter:
                  mcupak Miroslav Cupak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: