[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1045) Improve error message when binding fails

[Carlo de Wolf (JIRA)]

     [ https://jira.jboss.org/browse/EJBTHREE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved EJBTHREE-1045.
-------------------------------------

    Resolution: Out of Date


This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.

If you can reproduce this bug against a currently maintained version of 
JBoss EJB 3 please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>            Assignee: Andrew Rubinger
>             Fix For: trunk, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

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