Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-458

ConfigurationBasedEJBClientContextSelector should not throw an Error if JBoss Modules is not on the classpath

    XMLWordPrintable

Details

    Description

      The EJBCLIENT-417 fix changed the exception handling semantics of ConfigurationBasedEJBClientContextSelector from one where the use of 'moduleName' in the config in the absence of JBoss Modules on the classpath would result in ConfigXMLParseException to one where it results in NoClassDefFoundError. That's a major change in failure semantics and one the client-side applications using the library are unlikely to handle properly.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24148 [GSS](7.4.z) EJBCLIENT-458 - ConfigurationBasedEJBClientContextSelector should not throw an Error if JBoss Modules is not on the classpath

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          relates to

          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) EJBCLIENT-460 Add tests that run without jboss-module in the classpath

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

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: