Rob Castaneda wrote:
> Hi,
>
> >> Name Binding is not enough. You need to distribute EJB Home Object across
> the >>network too!
>
> Give me an example when this is not enough, and why I would have to
> redistribute the Home object?
You have to distribute before you redistribute. EJB clients need to gain access
to the Home object and whatever JNDI limitations you impose on your application
will limit your scalability. Maybe you don't need to distribute and redistribute
Home objects in a network. The real question is whether or not this is true.
Maybe you can give me an example.
> JNDI is a naming and directory service, some
> containers support dynamic class loading but this has nothing to do with
> JNDI and obtaining references.
It's not an issue of dynamic class loading but distribution over a network. EJB
Clients and Servers on different machines.
> What if my client is a C++ CORBA client
> accessing through the naming services' CORBA interface.
COSName is ok for certain things but Jini surrogates with COSName a re possible
too. It's very easy to write an IDL file and use COSName Stringified
representations of objects but you still need to distribute/proxy the object
somehow over the network.
> Why does it need to
> distribute the EJB Home object across the network??
Maybe not. Maybe all of your EJB clients and servers run on the same machine.
I'm not clear on this point either. .
Freeman Jackson
EJB Portal Management with Jini Connection Technology
Siliware, Inc.
Jini-JNDI Implementation: http://www.siliware.com/jinijndi.zip
Draft: http://www.siliware.com/whatisnds.htm
Draft: http://www.siliware.com/techsnds.htm
Home Page: http://www.siliware.com
Voice 201-239-0253
===========================================================================
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".
