Evan Ireland wrote:
> Freeman Jackson wrote:
> >
> > Is there another vendor that we can compare our Jini JNDI implementation with?
> > Seems to me that storing EJBs with Jini is a big plus.
>
> <vendor>
> Take a look at Sybase EAServer 3.5 - the JNDI API delegates to a CosNaming
> implementation that (in a clustered environment) uses replicated in-memory
> storage of name bindings. It's extremely fast, there is no single point of
> failure, and clients can provide multiple URLs for bootstrapping.
> </vendor>
Name Binding is not enough. You need to distribute EJB Home Object across the
network too!
Also It seems that a cross-vendor JNDI solution for EJB containers is very
important. SNDS network enables EJBs between different containers. It should work
with EAServer right-out-of-the box. Name space replication is easily achieved by
federating with Jini.
Download
http://www.siliware.com/jinijndi.zip and try it with EAServer and let me know if it
works.
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".
