[jboss-jira] [JBoss JIRA] (AS7-6410) Session beans are not bound to JNDI if there is a remote interface for a stateless bean

Tue May 7 05:58:53 EDT 2013

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

Bastian Katz commented on AS7-6410:
-----------------------------------

I can confirm there is a problem; the logs show bindings, but if I actually browse the JNDI, the bindings are not there. I am completely confused in which situation this happens, because if I deploy multiple modules, some of them are registered, and some aren't.

> Session beans are not bound to JNDI if there is a remote interface for a stateless bean
> ---------------------------------------------------------------------------------------
>
>                 Key: AS7-6410
>                 URL: https://issues.jboss.org/browse/AS7-6410
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, Naming, Remoting
>    Affects Versions: 7.1.1.Final
>         Environment: Ubuntu 12.10
>            Reporter: Jari Juslin
>            Assignee: jaikiran pai
>         Attachments: bugrepro.zip
>
>
> I have a session bean inside a jar, which in turn is inside an ear. If the session bean's interface is market with @Remote, JBoss 7.1.1 does not bind any beans in the package to JNDI. Change the @Remote to @Local or comment it out and binding takes place.
> The binding was checked both programmatically and from JBoss Management Console.
> No errors messages are printed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira