[jira] [Created] (DELTASPIKE-674) Possible regression due to changes in ConfigResolver

["Sven Panko (JIRA)" <ji...@apache.org>]

Sven Panko created DELTASPIKE-674:
-------------------------------------

             Summary: Possible regression due to changes in ConfigResolver
                 Key: DELTASPIKE-674
                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-674
             Project: DeltaSpike
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0.1
         Environment: Java 1.7.45, Mac OS X 10.9, Wildfly 8.1
            Reporter: Sven Panko


I just upgraded from 1.0.0 to 1.0.1 to see the fix in DELTASPIKE-648 in action. The problem now is: my property files are not picked up at all (I described my workaround in DELTASPIKE-648). I debugged the code to see that the changes are now in fact loading everything with the EAR classloader, but this loader fails to see my custom ConfigSourceProvider. 

One additional thing I changed between this issue and 648: I configured Wildfly to isolate supdeployments within an EAR, which was previously disabled. 1.0.0 still correctly sees my property files, but 1.0.1 does not. 

My suspicion is that the EAR classloader does not see the ConfigSourceProvider's inside the EJB jars. Since every lookup now uses this classloader it will never see any such implementations unless they are part of the "global" module that is comprised of the jars in the /lib directory of the EAR.



--
This message was sent by Atlassian JIRA
(v6.2#6252)