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

      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.

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

                Created:
                Updated:
                Resolved: