The biggest thing I like from EJB is the transaction support. Obviously not applicable in read-only queries, but in general business application programming there are plenty of places where the tx support is _very_ useful. As far as RMI goes, wrap the whole thing up in one ear, with local interfaces only, and _if_ you get to the point where you have a need for a swing client, or any other corba client for that matter, simply add remote interfaces.
The other good thing is it outlines a clear pattern for what code goes where. Using something like webwork (http://sf.net/projects/webwork) or struts should be enough to convince you to put your logic in one place, and your adapter code in another. my 2c cheers dim On Fri, 16 Nov 2001, Andrea Vicentini wrote: > Tom Copeland wrote: > > > One advantage to using a session bean is that later, if you want to > write a > > Swing client, you can do so and just have it call the same session > bean > > that your JSP is calling. > > OK, but it is dream, isn't it? > > Even more, the mail that started the thread sayd: > > > Why not just make the reads in a data access layer, put > > an object in the request and call the object in the JSP. > > So, if you do *have* a data access layer you may always be able to > call it from a Swing client too, don't you? > I could say, SessionBean (well... actually SF+SL+EB) are one way to > model a data access layer. A *distributed* one. > > Bye. > --Andrea Vicentini > > > ----- Original Message ----- > From: "Tom Copeland" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, November 15, 2001 16:50 > Subject: Re: Please Clarify the Need for Session Beans > > > > One advantage to using a session bean is that later, if you want to > write a > > Swing client, you can do so and just have it call the same session > bean > > that your JSP is calling. > > > > On the other hand, if that need ever arises, it wouldn't be too > hard just > > to write a session bean at that point. And if it doesn't, you've > saved > > some time and hassle! :-) > > > > Yours, > > > > Tom Copeland > > [EMAIL PROTECTED] > > 703-317-5193 > > > > > > > > Lawrence Marsh > > <lmarsh.cs@CLEARS To: > [EMAIL PROTECTED] > > TREAM.COM> cc: > > Sent by: A Subject: Re: > Please Clarify the Need for Session Beans > > mailing list for > > Enterprise > > JavaBeans > > development > > <EJB-INTEREST@JAV > > A.SUN.COM> > > > > > > 11/15/2001 07:17 > > AM > > Please respond to > > lmarsh.cs > > > > > > > > > > > > > > There is no need for a session bean in this scenario. This is just > what the > > Pet Store does for example. Also I don't see why it wouldn't be > reuseable > > to > > any other servers if it is well designed (and documented). Finally > you > > could > > wrap it in a Custom Tag so it could be reused by non Java > programers as > > well. > > > > Cheers > > > > Lawrence > > > > -----Original Message----- > > From: Mike Duffy [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, 15. November 2001 11:42 > > To: [EMAIL PROTECTED] > > Subject: Please Clarify the Need for Session Beans > > > > > > If I am just making simple reads from a data base to display > > information in a JSP (a user profile for example), why should I use > a > > session EJB? Why not just make the reads in a data access layer, > put > > an object in the request and call the object in the JSP. > > > > I understand that I would not have a "reusable component" that > could > > be deployed to other servers. But what are the other tradeoffs and > > advantages? > > > > Thanks! > > > > __________________________________________________ > > Do You Yahoo!? > > Find the one for you at Yahoo! Personals > > http://personals.yahoo.com > > > > > =========================================================================== > > 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". > > > > > > Visit us at http://www.clearstream.com > > > > IMPORTANT MESSAGE > > > > Internet communications are not secure and therefore Clearstream > > International does not accept legal responsibility for the contents > of this > > message. > > > > The information contained in this e-mail is confidential and may be > legally > > privileged. It is intended solely for the addressee. If you are not > the > > intended recipient, any disclosure, copying, distribution or any > action > > taken or omitted to be taken in reliance on it, is prohibited and > may be > > unlawful. Any views expressed in this e-mail are those of the > individual > > sender, except where the sender specifically states them to be the > views of > > Clearstream International or of any of its affiliates or > subsidiaries. > > > > END OF DISCLAIMER > > > > > =========================================================================== > > 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". > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > This email may contain confidential and proprietary information > which is > > for the sole use of the intended recipient. If you received this > email in > > error, please notify the sender and delete this email from your > computer. > > Any review, distribution or retransmission of or reliance on this > email by > > anyone other than the intended recipient is forbidden. > > > > > =========================================================================== > > 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". > > __________________________________________________ > Do You Yahoo!? > Find the one for you at Yahoo! Personals > http://personals.yahoo.com > > =========================================================================== > 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".
