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)?
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
