myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <...@myfaces.apache.org>
Subject [jira] Resolved: (EXTCDI-74) On Jboss 6 the BeanManagerProvider doesn't return the BeanManager due to classLoader differences
Date Thu, 11 Nov 2010 15:19:16 GMT

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

Gerhard Petracek resolved EXTCDI-74.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.9.1

> On Jboss 6 the BeanManagerProvider doesn't return the BeanManager due to classLoader
differences
> ------------------------------------------------------------------------------------------------
>
>                 Key: EXTCDI-74
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-74
>             Project: MyFaces CODI
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.9.0
>         Environment: JBoss  M4
>            Reporter: Rudy De Busscher
>            Priority: Minor
>             Fix For: 0.9.1
>
>         Attachments: extcdi-74.patch
>
>
> The method ClassUtils.getClassLoader(null) returns another ClassLoader during extension
initialization then during use of the class through a BeanManagerProvider.getInstance().getBeanManager().
> during initialization 
> cl = {org.jboss.classloader.spi.base.BaseClassLoader@17200}"BaseClassLoader@b14a51{vfs:///D:/3E/code/web/trunk/war/target/synaptiq.war}"
> during retrival
> cl = {org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@19651}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message