You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2015/10/07 20:49:26 UTC

[jira] [Updated] (DELTASPIKE-996) org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig fails for weblogic

     [ https://issues.apache.org/jira/browse/DELTASPIKE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek updated DELTASPIKE-996:
----------------------------------------
    Assignee: Mark Struberg

> org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig fails for weblogic
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DELTASPIKE-996
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-996
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: JJ Snyder
>            Assignee: Mark Struberg
>
> org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig fails when run against weblogic.  This is failing because ConfigResolver.configSources is getting populated during deployment using the Thread's context class loader.  At runtime the current Thread's context class loader is used to access configSources.  The problem is that the context class loaders are not the same.  Afaict there is nothing in the specs that says the context class loaders must be the same.  So I think the test is bad and needs to be written differently.  If I force the class loader to be the same in a debugger then I can make the test pass.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)