What I've done is to use a servlet (which acts as a proxie/controller) which
handles packaging the bean and sends it via an attribute so the jsp can just
get the bean and then use it as normal.
HTH,
Mark Sellers
Worldcom, Inc.
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Dan Hinojosa
Sent: Tuesday, August 15, 2000 2:35 PM
To: [EMAIL PROTECTED]
Subject: Best solution with JSP and EJB Session Beans
I have a session bean which access an entity bean which access a backend
DB. That is fine. I would like to keep the JSP from only using
<useBean><getProperty>and<setProperty> without the web developer knowing
what a portable remote object is. What is the best method to keep it
simple. Would I have to create a "Bean" that would create and narrow my
home and create the remote instance in the constructor? Everything else
would access the bean directly. Is there something else better?
--
Dan Hinojosa
Java & Lotus Notes Consultant
Java Certified Programmer
P.O. Box 4675
Albuquerque, NM 87196-4675
Telephone: (505) 262-0911
Email: [EMAIL PROTECTED]
WWW: http://www.digitalpriest.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".
