But I'm assuming this EJB/RMI scenario requires a RMI server in addition to
the EJB server. Why have the EJB server then?
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tye, Tim
> Sent: Tuesday, October 26, 1999 5:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> RMI is part of EJB. It is perfectly correct and legal to use RMI
> to implement beans that need to perform functions that are not
> allowed in the container. The RMI service can be called by EJB
> (in fact the EJB would not even know it was calling an RMI if
> coded correctly) and RMI can call EJB beans. The two are
> intended to work together. You are not leaving EJB if you
> implement some services in RMI.
>
> Perhaps some day, some one will figure out how to define a task
> bean that can do restricted operations. Until then RMI services
> are available.
>
> -----Original Message-----
> From: Ron Yust [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 26, 1999 5:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> Kinda like the old saying "if you don't like America, leave it".
> No, I want
> to change it. EJB has great promise, but it's going in directions I think
> is wrong.
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Tye, Tim
> > Sent: Tuesday, October 26, 1999 4:24 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: EJB Restrictions-- threads, io
> >
> >
> > Do it. RMI is the correct answer for many applications. It has
> > less overhead, and allows the designer to do anything.
> > However, RMI does not provide security, transaction control,
> > caching, or isolation like the EJB container.
> >
> > Always use the tool that meets the requirements of the job.
> >
> > Don't use EJB just because your management says it is hot.
> >
> >
> > -----Original Message-----
> > From: Ron Yust [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 26, 1999 2:57 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: EJB Restrictions-- threads, io
> >
> >
> > Paul,
> >
> > Wow! No static methods/data, no file i/o, no threads, no
> > sockets, no native
> > code. Sounds like EJB is an unruly teenager about to take the
> family car
> > out on a date. Geeesh, just neuter the EJB application! I may end up
> > sticking with my trusty old RMI server.
> >
> > -Ron
> >
> > ==================================================================
> > =========
> > 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".
>
> ==================================================================
> =========
> 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".
