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

[GSS](8.0.z) Upgrade jbossws-cxf from 7.3.0.Final to 7.3.1.Final

XMLWordPrintable

    • False
    • None
    • False

      Tag: https://github.com/jbossws/jbossws-cxf/releases/tag/jbossws-cxf-7.3.1.Final
      Hash: 201b49e680f909ece1537496bd1ac294f9a7a2e6
      Diff: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-7.3.0.Final...jbossws-cxf-7.3.1.Final

      Tag: https://github.com/jbossws/jbossws-common/releases/tag/jbossws-common-5.1.0.Final
      Hash: eb6e1bb06a4bf7cd2f84784c68312e9ec4c4e9c2
      Diff: https://github.com/jbossws/jbossws-common/compare/jbossws-common-5.0.0.Final...jbossws-common-5.1.0.Final

      Upgrade jbossws-cxf from 7.3.0 Final to 7.3.1.Final. Release notes : https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310050&version=12439419

      jbossws-common as a dependent will be upgraded from 5.0.0.Final to 5.1.0.Final.

      Some side note : 

      To fix   https://issues.redhat.com/browse/JBWS-4385  it creates a JAXPDelegateClassLoader for each webservice invocation, this seems not necessary to create classloader for each invocation. This can be improved by not creating this JAXPDelegateClassLoader in Servlet.init() instead of creating for each request. https://issues.redhat.com/browse/JBWS-4433 is for this improvement. This change is included in jbossws-cxf-7.3.1.Final release. 

       

              eleandro Éttore Leandro Tognoli
              istudens@redhat.com Ivo Studensky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: