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

(7.2.z) WFCORE-4346 - ChildFirstClassLoader and LegacyKernelServicesInitializer should allow exclusion of resources from the paren

    XMLWordPrintable

Details

    Description

      ChildFirstClassLoader and LegacyKernelServicesInitializer have hooks to allow tests to prevent classes from being loaded from the parent CL, but there's no way to prevent resources being loaded. In particular META-INF/services files, which bit us with https://github.com/wildfly/wildfly-core/pull/3685 as a META-INF/services file in the parent was being found when trying to load services for an interface in the child CL. The impls in the parent could not implement the child CL version of the interface. Excluding loading of the META-INF/services file in the paren solved the problem.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4405 Binary jar files in model-test

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          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) WFCORE-4346 ChildFirstClassLoader and LegacyKernelServicesInitializer should allow exclusion of resources from the paren

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-16580 (7.2.z) Upgrade WildFly Core from 6.0.12 to 6.0.14

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-lgao Lin Gao
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified