Uploaded image for project: 'Xerces2-J'
  1. Xerces2-J
  2. XERCESJ-1136

Expansion fails for URIs with non-ascii characters.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      The problem appears to be that a valid anyURI that occurs, for example, in a schemaLocation attribute on an import, is not properly escaped. Any attempt to create a URI from it fails, meaning that if it is relative it is not possible to resolve it against the base system ID. MalformedURIExceptions generated are swallowed silently, and the end result is a string which is supposed to be the expanded ID which is actually not expanded. If this string is passed to an XMLEntityResolver, the entity resolver can't deal with it properly.

      I think that provided that the hint is a valid anyURI, it should be correctly escaped and the proper expanded system id calculated.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            cps@decisionsoft.com Chris Simmons

            Dates

              Created:
              Updated:

              Slack

                Issue deployment