Hi David J,
Thanks for the explanation. So I can guess from this that
currently the names under which ejbs are bound to the corba and remote
jndi-naming contexts are not the values in jndi-name but the ones
generated via the jndi naming strategy. Will ping david B with this
question
Regards
Manu
On Thu, Mar 20, 2008 at 9:17 PM, David Jencks <[EMAIL PROTECTED]> wrote:
>
> On Mar 20, 2008, at 2:46 AM, Manu George wrote:
>
> > Hi,
> > When you are using ejb 2.1 you had to actually specify the
> > jndi-name/local-jndi-name in the openejb-jar.xml. I believe that that
> > name was used if you wanted to do a remote lookup etc. How was this
> > used for local lookups? Were the ejbs available in the application
> > specific jndi context with the local-jndi-name? I am not sure whether
> > this was how it was supposed to work?
>
> if you are talking about openejb 2.x, then the jndi-name and local-
> jndi-name are completely ignored for the java:comp context. You have
> to specify what you want your ejb-ref to point to by a combination
> of ejb-links in the DD and plan, automatic matchirng rules, setting
> up the module/plugin/configuration tree, and explicitly specifying
> the target gbean.
>
> The [local]jndi names were used to bind to the corba naming service
> and to bind to the non-j2ee openejb remote context that can be used
> for non-j2ee clients. I don't recall what the local-jndi-names were
> used for.
>
>
>
> >
> > Currently I believe we are actually ignoring those names and
> > constructing jndi names based on the same strategy we use for ejb3. Am
> > I right about this? If so isn't this a bug that breaks backward
> > compatibility? As long as we use ejb-refs there won't be any problem
> > currently but if you try to access from a remote client the jndi name
> > used will be different.
>
> I'm not sure what is happening now :-)
> thanks
> david jencks
>
> >
> > Regards
> > Manu
>
>
