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

[GSS](7.4.z) EJBCLIENT-458 - ConfigurationBasedEJBClientContextSelector should not throw an Error if JBoss Modules is not on the classpath

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.4.9.CR1, 7.4.9.GA
    • None
    • EJB
    • None

      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.

              rhn-support-ivassile Ilia Vassilev
              rhn-support-ivassile Ilia Vassilev
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: