tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Blevins (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENEJB-712) issues with KeyedCollection
Date Fri, 01 Feb 2008 03:47:08 GMT

     [ https://issues.apache.org/jira/browse/OPENEJB-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Blevins updated OPENEJB-712:
----------------------------------

    Fix Version/s: 3.0.x

throwing this into the 3.0.x bucket in hopes for fixing it in next release

> issues with KeyedCollection 
> ----------------------------
>
>                 Key: OPENEJB-712
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-712
>             Project: OpenEJB
>          Issue Type: Bug
>    Affects Versions: (trunk/openejb3)
>            Reporter: Jarek Gawor
>             Fix For: 3.0.x
>
>
> The following used to work fine:
> EjbRef ref = new EjbRef();
> SessionBean.getEjbRef().add(ref);
> Now the following is required:
> EjbRef ref = new EjbRef();
> ref.setEjbRefName(<name>);
> SessionBean.getEjbRef().add(ref);
> because the reference name is used as a key in the KeyedCollection. If the reference
name is not set first, a reference is added to the KeyedCollection with a null key. And if
there are multiple references added this way, only the last one will be in the map.
> Maybe somekind of an exception should be thrown or a warning logged if a null key is
used so that it would be easier to find problems like this?

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


Mime
View raw message