Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5588

WF Core StringBytesLengthValidator should not use error message considering characters

    XMLWordPrintable

Details

    • Hide

      Add the node identifier attribute under transaction subsystem and start the server. The identifier string length is 23 but serve won't be started. If system default encoding is UTF-8.

      The identifier needs to be composed from characters e.g. U+10348 as mentioned on wikipedia page https://en.wikipedia.org/wiki/UTF-8
      (jira does not support this character to be pasted directly here)

      <core-environment node-identifier="">
      Show
      Add the node identifier attribute under transaction subsystem and start the server. The identifier string length is 23 but serve won't be started. If system default encoding is UTF-8 . The identifier needs to be composed from characters e.g. U+10348 as mentioned on wikipedia page https://en.wikipedia.org/wiki/UTF-8 (jira does not support this character to be pasted directly here) <core-environment node-identifier="">

    Description

      Current implementation of class StringBytesLengthValidator which is used by TransactionSubsystemRootResourceDefinition for validation of node-identifier element prints error message in format

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"

      but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the node id that the string has length smaller than 23 but the message says that it's bigger.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1702 WF Core StringBytesLengthValidator should not use error message considering characters

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5456 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha5

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              chaowan@redhat.com Chao Wang
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: