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

[GSS](7.0.z) Jar sub deployment has as first dependency parent ear

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.4.CR1, 7.0.4.GA
    • None
    • Modules
    • None
    • Hide

      1. Create ear file with war and jar file in ear main directory
      2. Add jar file to war class path via war MANIFEST.MF
      3. Add method to class in jar file instantiating class from server implicit modules
      4. Add jar file containing class from step #3 but different behavior to ear/lib directory
      5. Invoke method from step #3 from war file
      ERROR: Class from ear/lib directory is instantiated instead of class from implicit module

      Show
      1. Create ear file with war and jar file in ear main directory 2. Add jar file to war class path via war MANIFEST.MF 3. Add method to class in jar file instantiating class from server implicit modules 4. Add jar file containing class from step #3 but different behavior to ear/lib directory 5. Invoke method from step #3 from war file ERROR: Class from ear/lib directory is instantiated instead of class from implicit module
    • EAP 7.0.4

    Description

      Jar file included in ear main directory is resolved as sub deployment with parent ear as first dependency.
      Therefore jar files contained in ear/lib directory have priority before implicit modules when class is created inside jar file.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5267 Jar sub deployment has as first dependency parent ear

          • 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.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6603 (7.0.z) Upgrade WildFly Core from 2.1.9.Final-redhat-1 to 2.1.10.Final

          • 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.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4635 Create test for [JBEAP-4241] Jar sub deployment has as first dependency parent ear

          • 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.
          • Verified

          Activity

            People

              vpakan Vlado Pakan (Inactive)
              vpakan Vlado Pakan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: