Uploaded image for project: 'Seam Faces'
  1. Seam Faces
  2. SEAMFACES-50

Extra BeanManagerProviders in service file results in no BM found on beta-1

    Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      remove JNDI BMPs from faces services

      Show
      remove JNDI BMPs from faces services

      Description

      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

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                nickarls Nicklas Karlsson
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: