[jboss-jira] [JBoss JIRA] (WFLY-12462) Incompatible conflicting binding Exception and EJB naming

[Cheng Fang (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781455#comment-13781455 ] 

Cheng Fang commented on WFLY-12462:
-----------------------------------

I couldn't reproduce it either, with the attached reproducer.  There is no particular restriction on the naming of ejb bean interface and classes, and this is odd that renaming ejb bean classes should make such a difference.  Do you see the same error when you start wildfly default profile (./standalone) instead of the full profile? Can try the latest WildFly snapshot or [18.0.0.Beta1 |https://wildfly.org/downloads/]?

> Incompatible conflicting binding Exception and EJB naming
> ---------------------------------------------------------
>
>                 Key: WFLY-12462
>                 URL: https://issues.jboss.org/browse/WFLY-12462
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, EJB
>    Affects Versions: 17.0.1.Final
>         Environment: MacOS High Sierra
>            Reporter: Alexey Usharovski
>            Assignee: Cheng Fang
>            Priority: Minor
>         Attachments: server.log.zip, simplewebapp-lesson-6-ejb.zip, war-content.txt.zip
>
>
> Wired exception for very simple EJB with @Remote annotated interface in time of deploy to WildFly 17.0.1.Final
> {code:java}
> @Stateless 
> public class UserServiceImpl implements UserServiceRemote {  
>       @Override 
>       public List<UserRepr> getAllUsers() { 
>           return null; 
>       } 
> }
> @Remote 
> public interface UserServiceRemote {  
>      List<UserRepr> getAllUsers(); 
> }
> {code}
> The exception is
> {code}
> Caused by: java.lang.IllegalArgumentException: WFLYEE0047: Incompatible conflicting binding at java:jboss/exported/simple-webapp/UserServiceImpl!ru.geekbrains.jsf.UserServiceRemote 
> source: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2 at 6aba1c4b"}, 
> "WFLYCTL0412: Required services that are not installed:" => [ "jboss.deployment.unit.\"simple-webapp.war\".beanmanager", "jboss.deployment.unit.\"simple-webapp.war\".WeldStartService" ], 
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.deployment.unit.\"simple-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager]", 
> "jboss.deployment.unit.\"simple-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager, jboss.deployment.unit.\"simple-webapp.war\".WeldStartService]" ] }
> {code}
> Notice that problem could be resolved by undeploy and Wildfly server restart. May be something wrong with JNDI content?
> I've tried to look through the web console but found nothing interesting.
> Full application code on GitHub https://github.com/usharik/simplewebapp/tree/lesson-6-ejb



--
This message was sent by Atlassian Jira
(v7.13.5#713005)