[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1545) @RemoteBinding can clash w/ Default Remote Binding

[Aleksander Adamowski (JIRA)]

    [ https://jira.jboss.org/browse/EJBTHREE-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12540718#action_12540718 ] 

Aleksander Adamowski commented on EJBTHREE-1545:
------------------------------------------------

For the record and search engines' indexes, here's the characteristic part of the exception that occurs, taken straight from the related post on community forum (http://community.jboss.org/message/202805):

09:32:56,213 INFO [EJBContainer] STOPPED EJB: com.powerlogic.app.facade.AppFacadeImpl ejbName: AppFacadeImpl
09:32:56,213 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jcompany_jsf_modelo.jar,name=AppFacadeImpl,service=EJB3 state=Create
java.lang.ClassCastException: $Proxy421 cannot be cast to javax.naming.Context
 at org.jboss.util.naming.Util.createSubcontext(Util.java:70)
 at org.jboss.util.naming.Util.bind(Util.java:104)
 at org.jboss.util.naming.Util.bind(Util.java:91)
 at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:901)
 at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:886)
 at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bind(JndiSessionRegistrarBase.java:875)
 at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.bindEjb(JndiSessionRegistrarBase.java:150)
 at org.jboss.ejb3.session.SessionContainer.lockedStart(SessionContainer.java:174)
 at org.jboss.ejb3.session.SessionSpecContainer.lockedStart(SessionSpecContainer.java:606)
 at org.jboss.ejb3.stateless.StatelessContainer.lockedStart(StatelessContainer.java:247)
 at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:879)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
 at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
 at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
 at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
 at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
 at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
 at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
 at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
 at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
 at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)

This is a really serious issue, completely unexpectable and with a cryptic error message in the logs. Who would expect that the container would bind an EJB under a name colliding with what the developer explicitly set using an annotation, completely hosing the EJB's deployment?

We've been bitten by this problem when migrating an app from JBoss 4.2 Community to JBoss 5 Enterprise Application Platform.

I think it deserves to be classified as a serious regression.

Such surprise bugs also seriously harm the image of JBoss as an enterprise class solution in an organization.


> @RemoteBinding can clash w/ Default Remote Binding
> --------------------------------------------------
>
>                 Key: EJBTHREE-1545
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1545
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: proxy
>            Reporter: Andrew Lee Rubinger
>            Assignee: Andrew Lee Rubinger
>             Fix For: Unscheduled
>
>
> @Stateless(name="MyBean")
> @Remote(MyRemote.class)
> @RemoteBinding(jndiBinding="MyBean")
> class MyBean{...}	
> ...produces:
> /MyBean - Explicit from @RemoteBinding
> /MyBean/remote - Default Remote Business Interface Proxy Binding	
> ...and results in CCE.
> Propose not applying default remote business interface binding if at least 1 @RemoteBinding is specified.

-- 
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