org.jboss.weld.exceptions.DeploymentException

WELD-000163: Non-unique bean deployment identifier detected:


Solutions on the web462

Solution icon of github
WELD-000163: Non-unique bean deployment identifier detected:

Solution icon of googlegroups
via Google Groups by PCB, 7 months ago
WELD-001410: The injection point has non-proxyable dependencies: [BackedAnnotatedField] @Inject private org.wildfly.swarm.container.runtime.RuntimeDeployer.defaultDeploymentCreator

Solution icon of googlegroups
WELD-001410: The injection point has non-proxyable dependencies: [BackedAnnotatedField] @Inject private org.wildfly.swarm.container.runtime.RuntimeDeployer.defaultDeploymentCreator

Solution icon of web
via com.br by Unknown author, 1 year ago
WELD-001410: The injection point [BackedAnnotatedParameter] Parameter 2 of [BackedAnnotatedConstructor] @Inject public app.controller.IndexController(Result, Socket) has non-proxyable dependencies

Solution icon of googlegroups
via Google Groups by João Batista de Andrade, 1 year ago
WELD-000072: Bean declaring a passivating scope must be passivation capable. Bean: Managed Bean [class br.com.jb.login.session.UsuarioSessao] with qualifiers [@Any @Default]

Solution icon of java
via Java.net JIRA by fatihbalki, 1 year ago
WELD-001414 Bean name is ambiguous. Name javax.enterprise.context.conversation resolves to beans [org.jboss.weld.bean-LPISService_jar-Built-in-javax.enterprise.context.Conversation, Managed Bean [class org.jboss.weld.conversation.ConversationImpl] with qualifiers [@Default @Named @Any]]

Solution icon of java
via Java.net JIRA by fatihbalki, 1 year ago
WELD-001414 Bean name is ambiguous. Name javax.enterprise.context.conversation resolves to beans [org.jboss.weld.bean-LPISService_jar-Built-in-javax.enterprise.context.Conversation, Managed Bean [class org.jboss.weld.conversation.ConversationImpl] with qualifiers [@Default @Named @Any]]

Solution icon of oraclecommunity
via Oracle Community by bergler, 1 year ago
/lib to bring them into the application class loader. Failed: It seems that its not possible to have bean archives in APP-INF/lib. Can't blame oracle for this, its a non-standard extension anyway. - combining the module classloaders with weblogic

Solution icon of web
via blogspot.com by Unknown author, 1 year ago
WELD-001414 Bean name is ambiguous. Name omnifaces_ViewScopeProvider resolves to beans Managed Bean [class org.omnifaces.cdi.viewscope.ViewScopeManager] with qualifiers [@Any @Default @Named], Managed Bean [class org.omnifaces.cdi.viewscope.ViewScopeManager] with qualifiers [@Any @Default @Named]

Solution icon of web
via com.br by Unknown author, 11 months ago
WELD-001414 Bean name is ambiguous. Name dadospessoais resolves to beans [Managed Bean [class br.ueg.com.aulasjamil.DadosPessoais] with qualifiers [@Any @Default @Named], Managed Bean [class br.ueg.com.aulasjamil.Intereces] with qualifiers [@Any @Default @Named]]

Stack trace

  • org.jboss.weld.exceptions.DeploymentException: WELD-000163: Non-unique bean deployment identifier detected: at org.jboss.weld.bootstrap.DeploymentVisitor.visit(DeploymentVisitor.java:51) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:430) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:95) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Once, 2 days ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago