[seam-issues] [JBoss JIRA] Commented: (SEAMFACES-50) Extra BeanManagerProviders in service file results in no BM found on beta-1
[
https://jira.jboss.org/browse/SEAMFACES-50?page=com.atlassian.jira.plugin...
]
Nicklas Karlsson commented on SEAMFACES-50:
-------------------------------------------
To make matters worse, this doesn't always fix the issue. Sometimes it fails in the
same way first time the servers is started but starts working after you re-deploy the
application.
Extra BeanManagerProviders in service file results in no BM found on
beta-1
---------------------------------------------------------------------------
Key: SEAMFACES-50
URL: https://jira.jboss.org/browse/SEAMFACES-50
Project: Seam Faces
Issue Type: Bug
Components: Build & Distribution
Affects Versions: 3.0.0.Alpha3
Reporter: Nicklas Karlsson
The faces modules contains the service file for BeanManagerProvider that has
org.jboss.weld.extensions.beanManager.DefaultJndiBeanManagerProvider
org.jboss.weld.extensions.beanManager.JBossJndiBeanManagerProvider
in addition to it's own
org.jboss.seam.faces.beanManager.FacesServletContextBeanManagerProvider
Since the weld extensions also carry the Default/JBoss JNDI providers we end up with 5
providers for that dependency combination. For some reason (classloading?), in the
beta1-AS Pete provided this is a problem - resulting in *no* BeanManagers being found
(which results in a crash when the faces module SeamExternalContext is set up for the
first time)
Removing the JNDI based BeanManagerProviders from faces appears to help the issue itself
but it leaves the faces module completely dependent on other modules for BM access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira