Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-1855

KEN XSD Schema validation for notifications being sent into KEN via the XML based String input service fails for non-UTF-8 DBs

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 0.9.2
    • Fix Version/s: 0.9.3
    • Component/s: Database, Development
    • Labels:
      None
    • Rice Module:
      KEN
    • Application Requirement:
      Rice

      Description

      When running the recipes sample application against an Oracle 10g DB with non-UTF-8 encoding, the sending of the notification fails.

      See screen shot for log.

      The code in here demonstrates this: https://test.kuali.org/svn/rice_bootcamps/trunk/cornell_april_2008/recipes_reference/src/main/java/edu/sampleu/recipe/document/maintainable/impl/RecipeMaintainableImpl.java

      When you run against a non-UTF-8 DB you get the attached error. When you run against a UTF-8 DB, it works fine.

      I think our problem is that when we retrieve the XSD used to validate the XML string representation of a notification, the service behind the scenes tries to validate with the XSD and fails b/c it didn't properly grab the XSD and any special characters out of the DB.

        Attachments

          Activity

          Hide
          agodert Aaron Godert (Inactive) added a comment -

          Aaron,

          Here's what I get when requesting the encoding on our oracle 10g database with the following sql: select * from nls_database_parameters
          where parameter='NLS_CHARACTERSET';

          WE8ISO8859P1 ISO 8859-1 West European SB, ASCII

          I'm not sure if this is exactly what you want to know. I googled it and tried the sql.

          Mike

          Show
          agodert Aaron Godert (Inactive) added a comment - Aaron, Here's what I get when requesting the encoding on our oracle 10g database with the following sql: select * from nls_database_parameters where parameter='NLS_CHARACTERSET'; WE8ISO8859P1 ISO 8859-1 West European SB, ASCII I'm not sure if this is exactly what you want to know. I googled it and tried the sql. Mike
          Hide
          agodert Aaron Godert (Inactive) added a comment -

          This bug prevents people using certain encoding types at the DB from being able to send notifications via the service that takes the String of XML.

          Show
          agodert Aaron Godert (Inactive) added a comment - This bug prevents people using certain encoding types at the DB from being able to send notifications via the service that takes the String of XML.
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          Could not reproduce against a non-UTF8 10g instance. This should be tested on a system with some incompatible default charset.

          Show
          ahamid Aaron Hamid (Inactive) added a comment - Could not reproduce against a non-UTF8 10g instance. This should be tested on a system with some incompatible default charset.
          Hide
          ahamid Aaron Hamid (Inactive) added a comment -

          Could not reproduce this with non utf8 Oracle 10g db and foreign locale.

          Show
          ahamid Aaron Hamid (Inactive) added a comment - Could not reproduce this with non utf8 Oracle 10g db and foreign locale.

            People

            • Assignee:
              ahamid Aaron Hamid (Inactive)
              Reporter:
              agodert Aaron Godert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: