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

Early initialize WSSConfig (including BouncyCaste JCE provider registration)

    XMLWordPrintable

Details

    Description

      We should move the WSSConfig init earlier in the WS subsystem startup.

      Moreover on WildFly we have BouncyCastle JCE provider in org.bouncycastle module [1], so we can set a proper module dependency and avoid requiring the current JDK to have BC installed.

      [1] https://github.com/wildfly/wildfly/commit/81bdfd083d855ded4bb6ce7ea1d56791fed20203

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JBWS-3681 Add to testsuite profiles allowing to exclude tests requiring Bouncy Castle JCE provider or unlimited strength cryptography installed

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBWS-3662 dynamic registration of Bouncy Castle JCE provider in cxf specific tests

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-support-asoldano Alessio Soldano
              rhn-support-asoldano Alessio Soldano
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: