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? JNDI is a naming and directory service, some
containers support dynamic class loading but this has nothing to do with
JNDI and obtaining references. What if my client is a C++ CORBA client
accessing through the naming services' CORBA interface. Why does it need to
distribute the EJB Home object across the network??
>According to NS411 they don't even bundle with JNDI!
>http://www.borland.com/devsupport/appserver/faq/VisiNamingServiceFAQ.html
>How can you say it even supports EJB?
You're looking at an FAQ for the VisiBroker Naming service(CORBA), not the
Inprise Application Server. Download IAS4 and try it. Before you claim that
it doesnt support EJB.
>It seems that you need a seperate Pluggable Backing Store for storing
objects.
>See NS200
http://www.borland.com/devsupport/appserver/faq/VisiNamingServiceFAQ.html
>Therefore clustering is not out-of-the box!
Um, it actually ships with the Application Server product. Configuring
Master Slaves is done by setting Java Properties.... yes out of the box, or
straight off the download ;-)
Different implementations of JNDI are layered upon different technologies to
allow interoperability between technologies. Can you explain to me how a C++
CORBA client would obtain references through a JINI based JNDI naming
service? I'm not sure if it could cater for such a heterogenous environment.
kind regards,
-Robert
----- Original Message -----
From: Freeman Jackson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 19, 2000 11:56 AM
Subject: Re: replicated name services?
> 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".
>
===========================================================================
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".
