Evan Ireland wrote:
> Freeman Jackson wrote:
> >
> > 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!
>
> <vendor>
> Of course. You didn't ask about that. We support that too. There is no
> point having a highly available name service if all it can serve up is
> home object references that aren't also fault tolerant. EAServer supports
> transparent automatic failover of home and remote object references
> (all EJB types - entity, stateful, stateless and CORBA equivalents).
> </vendor>
>
> > 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.
>
> Sorry, I don't have time to do this at the moment. Can it be used for
> binding serialzable objects (as opposed to object references)?
Yeah but you still need to serialize the object via RMI, generate additional stubs and
skeletons for the RMI process, distribute the additonal stubs and skeletons on both the
EJB client and EJB server side, and map your RMI references back into LDAP or COSName.
In
addition, for each and every potential EJB client-server permutation across the
enterprise.
The additional administration overhead and complexities with the LDAP or COSName
approach
increases exponentially when you add more EJB objects. You can get away with it when
it's
two or three network-enabled EJBs but once you have hundreds/thousands/millions of
network-enabled EJBs, and stubs and skeletons, it starts to fall apart real quick.
Freeman Jackson
EJB Portal Management with Jini Connection Technology
Siliware, Inc.
Jini-JNDI Implementation: http://www.siliware.com/jinijndi.zip
Primary Draft: http://www.siliware.com/whatisnds.htm
Secondary 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".
