I'm currently trying to solve a tricky class loading issue connected to Spring, CDI and Uber Jars. Here's the scenario:
- Remote Uber Jar contains CDI module
- Our Hot Rod client use newer version of JBoss Logging which is present in Wildfly/EAP modules
- However EAP and Wildfly will load (and make available for deployment) their own version of JBoss Logging [1]
- The easiest fix for this is to relocate JBoss Logging package in Uber Jar
- Spring module requires some classes from Infinispan Common and they in turn need BasicLogger from JBoss Logging
- If we relocate JBoss Logging and will try to use Uber Jar with Spring - we will end up with classloading issue [2]
So it seems the best approach is to make Spring depend on Uber Jars instead of "small ones". Of course, users who use small jars will probably be affected by this change (they would have to either accept using Uber Jars or exclude them in their poms and add dependencies manually).
Is anyone against this solution? JIRA tracking ticket: [3].
Thanks
Sebastian