Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-3709

Improve handler-chains.xml parsing

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4, nightly
    • jaxws
    • None

    Description

      Right now the handler-chains.xml file is parsed using JAXB. The problem with JAXB parsing is that it returns null for an invalid qname. For example, when the namespace of the qname cannot be resolved. So for example, when the handler-chains.xml contains an invalid qname for service-name or port-name and JAXB returns null then the HandlerResolver will treat it as if the service-name/port-name was not specified at all. And therefore HandlerResolver will return a handler that it should not.

      Attachments

        Activity

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

          People

            gawor@mcs.anl.gov Jarek Gawor
            gawor@mcs.anl.gov Jarek Gawor
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment