geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <>
Subject Re: Is GeronimoMappedName still required ?
Date Tue, 22 Feb 2011 04:02:05 GMT
We may not need it if we prune out the things from the JNDI tree we don't want OpenEJB to build.

We used to use it as a way to merge the OpenEJB built JNDI tree with the Geronimo built one.
 The OpenEJB one was in "front" and the Geronimo one was in back.  So the OpenEJB tree had
links to all the Geronimo tree items Geronimo wanted to control.  Now it's the reverse.


On Feb 21, 2011, at 5:57 PM, Ivan wrote:

> OK, seems that no one remembered that history, I also noticed that file is
> added long long ago. I think that the only way is to remove it, and check
> whether everything still works well.
> 2011/2/19 Ivan <>
>> Hi,
>> I found a GeronimoMappedName in the EJB deployment chain, and it will
>> configure the mapped name for some of jndi staff. Seems that mapped name is
>> used to configured server specified jndi name, but I did not find the
>> configured jndi:java:comp/geronimo/env/ namespace in Geronimo JNDI tree now
>> (From the history, it seems that that tree is created in the
>> EJBDeploymentGBean in the past). I am wondering that do we still require it
>> ? As it will configure the resource refer to an nonexisting place.
>> Thanks.
>> --
>> Ivan
> -- 
> Ivan

View raw message