You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Barnabas Bodnar (JIRA)" <ji...@apache.org> on 2015/03/25 22:15:56 UTC
[jira] [Created] (TOMEE-1532) EJB-references declared at
superclasses residing in libraries aren't considered
Barnabas Bodnar created TOMEE-1532:
--------------------------------------
Summary: EJB-references declared at superclasses residing in libraries aren't considered
Key: TOMEE-1532
URL: https://issues.apache.org/jira/browse/TOMEE-1532
Project: TomEE
Issue Type: Bug
Affects Versions: 1.7.1
Reporter: Barnabas Bodnar
EJB-references (both injected and via JNDI) declared at a superclass of an EJB are ignored by TomEE 1.7.1, if the superclass resides in a library-module.
Application-servers from the JBoss7-family, as well as Oracle Weblogic 12 and IBM Websphere 8 set such EJB-references correctly.
The attached application demonstrates this behavior: the startup-singleton "ReferencingEJB" has a locally declared reference to "EJB2" and inherits references to "EJB1" declared in the superclass "EJBSuperclass" residing in a library-module. The availability of the EJB-references is checked in a post-construct-method and produces the following output:
{noformat}
===========================================================================
Local injected EJB-reference: set
Local EJB-reference in the JNDI-context: set
Inherited injected EJB-reference: not set
Inherited EJB-reference in the JNDI-context: not set
===========================================================================
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)