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

Thread safety in XMLFaultCode

Rank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.4
    • 1.4
    • None
    • None

    Description

      The way XMLFaultCode handles custom fault codes by modifying CUSTOM_SOAP11_ONLY enum value is just not thread safe. I think the XMLFaultCode should be turned into a class and each custom fault code would be a separate XMLFaultCode instance.

      Attachments

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

          People

            Unassigned Unassigned
            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