[jboss-jira] [JBoss JIRA] Resolved: (JBAS-8689) JNDI namespace doesn't contain beans with inherited business interfaces anymore since 6.0.0.CR1
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Tue Nov 30 10:33:09 EST 2010
[ https://jira.jboss.org/browse/JBAS-8689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo de Wolf resolved JBAS-8689.
---------------------------------
Resolution: Rejected
> JNDI namespace doesn't contain beans with inherited business interfaces anymore since 6.0.0.CR1
> -----------------------------------------------------------------------------------------------
>
> Key: JBAS-8689
> URL: https://jira.jboss.org/browse/JBAS-8689
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB3, Java EE APIs
> Affects Versions: 6.0.0.CR1
> Environment: java version "1.6.0_18"
> Reporter: Tobias Grundmann
> Assignee: Carlo de Wolf
> Labels: jndi, lookup
> Attachments: test.zip
>
>
> Since 6.0.0.CR1 the lookup of EJBs via jndi doesnt' work anymore if the bean itself doesn't "implement" a business interface but inherits it. I''ve tried this with @Local annotated interfaces and both the old JBoss syntax ("appName/beanName/local") and the newly supported (as of 6.0.0.CR1) portable ones ("java:global/appName/moduleName/beanName!InterfaceFQN").
> "Implements" here means actually specifying an implements statement at the class definition:
> @Local
> interface IBeanA {}
> @Stateful
> class BeanA implements IBeanA {} //lookup of BeanA works
> @Stateful
> class BeanB extends BeanA {} //lookup of BeanB doesn't work
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list