Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-3887

Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • None

      JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions)

            [JBWS-3887] Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

            Bartosz Baranowski added a comment -

            It seems it is no longer relevant.

            Bartosz Baranowski added a comment - It seems it is no longer relevant.

            RH Bugzilla Integration added a comment -

            Ivo Studensky <istudens@redhat.com> changed the Status of bug 1203181 from NEW to CLOSED

            RH Bugzilla Integration added a comment - Ivo Studensky <istudens@redhat.com> changed the Status of bug 1203181 from NEW to CLOSED

            Ivo Studensky added a comment -

            What about this issue, is it still relevant? You stated on the referenced bz that it works.

            Ivo Studensky added a comment - What about this issue, is it still relevant? You stated on the referenced bz that it works.

            RH Bugzilla Integration added a comment -

            baranowb <bbaranow@redhat.com> changed the Status of bug 1203181 from ASSIGNED to NEW

            RH Bugzilla Integration added a comment - baranowb <bbaranow@redhat.com> changed the Status of bug 1203181 from ASSIGNED to NEW

            RH Bugzilla Integration added a comment -

            Ivo Studensky <istudens@redhat.com> changed the Status of bug 1203181 from NEW to ASSIGNED

            RH Bugzilla Integration added a comment - Ivo Studensky <istudens@redhat.com> changed the Status of bug 1203181 from NEW to ASSIGNED

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-cservice-bbaranow Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: