geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap (JIRA)" <>
Subject [jira] Closed: (GERONIMO-2778) Deployer should always fill in required <local> or <remote> interfaces elements in <ejb-ref>
Date Tue, 29 May 2007 18:24:15 GMT


Prasad Kashyap closed GERONIMO-2778.

       Resolution: Fixed
    Fix Version/s:     (was: 2.0-M4)

This has now been fixed. David Blevins too confirmed this for me.

> Deployer should always fill in required <local> or <remote> interfaces elements
in <ejb-ref>
> --------------------------------------------------------------------------------------------
>                 Key: GERONIMO-2778
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0-M2, 2.0-M5
>            Reporter: Prasad Kashyap
>            Priority: Critical
>             Fix For: 2.0-M5
> For a proper ejb-ref to an EJB 3.0 bean (i.e. a business interface) it *must* have the
<remote> or <local> and must *not* have the <home> or <local-home>.
> These can only be omitted in the case of dependency injection where the code using the
@EJB to generate a metadata-complete ejb-ref should *always* fill in the <remote> element
of the <ejb-ref> element.  If the user does not specify the 'beanInterface' attribute
of the @EJB annotation, then the code building the reference must use the class type of the
field or method as the value of '<remote>'.
> There is an edge case where you truly do not know if the @EJB is pointing to a local
object or a remote object and therefore don't know whether to build a ejb-ref or an ejb-local-ref.
 For OpenEJB we build an ejb-ref and flag it as being "ambiguous", then in the jndi building
code we try to resolve it against the full list of available ejbs.  We'll have to figure out
some way to communicate this edge case to the ejb naming builder so we can deal with it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message