openejb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <david.blev...@visi.com>
Subject Re: Regarding jndi names of EJB 2.1 beans
Date Wed, 02 Apr 2008 08:20:28 GMT

On Apr 2, 2008, at 1:05 AM, David Blevins wrote:
> Just an FYI also, the legacy <jndi-name> element applies strictly to  
> javax.ejb.EJBHome interfaces as it always did.  Make sure you're not  
> testing a EJB 3.0 style business interface; the new <jndi> element  
> covers those as well as legacy interfaces.

Seemed pretty clear you're talking only about 2.1 views, but felt the  
need to be explicit just in case :)  (never hurts)

-David

>
> On Apr 2, 2008, at 12:36 AM, Manu George wrote:
>> I just saw the output that is printed to the log as JNDI name for one
>> of the samples. Maybe its just the logging for the jndi names that is
>> not picking it up. Let me verify this
>>
>> Regards
>> Manu
>>
>> On Wed, Apr 2, 2008 at 1:47 AM, David Blevins  
>> <david.blevins@visi.com> wrote:
>>>
>>>
>>> On Mar 31, 2008, at 4:19 AM, Manu George wrote:
>>>> Hi,
>>>>  Previously we used to have a jndi-name in the openejb-jar.xml for
>>>> geronimo. Currently for EJB 2.1 beans we dont use the values in  
>>>> that
>>>> element and instead generate the name in the same way we do for EJB
>>>> 3.0. Is this by design or an issue?
>>>>
>>>
>>> This should be supported.  The code to convert those elements to the
>>> new ones are there:
>>>
>>> OpenEjb2Conversion.java:
>>>
>>>            for (String name : enterpriseBean.getLocalJndiName()) {
>>>                deployment.getJndi().add(new
>>> org.apache.openejb.jee.oejb3.Jndi(name, "LocalHome"));
>>>            }
>>>
>>>            for (String name : enterpriseBean.getJndiName()) {
>>>                deployment.getJndi().add(new
>>> org.apache.openejb.jee.oejb3.Jndi(name, "RemoteHome"));
>>>            }
>>>
>>>
>>> Have you been able to verify that they don't work?
>>>
>>> -David
>>>
>>>
>>
>
>


Mime
View raw message