Dan,
A good pattern to use is a facade. Create a simple JavaBean that talks to the session
bean rather than the session bean
talking directly. This bean could return objects that the web team understands, i.e.
primitives, strings, and arrays of
the forementioned.
Chris
-----Original Message-----
From: Dan Hinojosa [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 15, 2000 3: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".
