Rickard �berg wrote:
> On Sun, 18 Jun 2000 06:51:14 -0700, Freeman Jackson
> <[EMAIL PROTECTED]> wrote:
>
> >Rickard �berg wrote:
> >
> >> On Sat, 17 Jun 2000 16:29:22 MDT, Venkat Muthusamy <[EMAIL PROTECTED]>
> >> wrote:
> >> >If I want to access one ejb to another.what is the way the flow goes?
> >> >
> >> >Is it directly communicate to another one with Interface
> >> >
> >> >or the floe goes all the steps such as
> >> >RMI-stub/skeleton-EjbServer-Container-EJB
> >> >
> >> >If both are in same m/c.
> >>
> >> This is vendor-specific, although most containers will optimize for the
> >> VM-local case so that no network code is executed.
> >>
> >> What you can always count on is the call semantics defined in the EJB
> >> spec. How this is implemented will differ between implementations. Some
> >> wont even have a RMI-stub (since a distribution protocol isn't strictly
> >> required).
> >
> >Seems that a Jini/JavaSpaces implementation of JNDI can help here. Each ejb can
> >use this approach to store and retrieve Home Object. No more 1 machine
> >restrictions.
>
> Uhm, excuse my ignorance, but what exactly does a Jini-based
> JNDI-implementation have to do with the above question?
I'm new to EJB but it seems to me that you have to use the JNDI context for
EJB-TO-EJB interoperability. Maybe you can do it another way. Forgive me if I'm
mistaken.
Thanks
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
