Paul,
If you consider that servlets can be the layer between presentation and
data, certainly servlets can appropriately interface with EJB's.
As for JSPs, I agree that doing something directly from a JSP to an EJB is a
dubious way to go, but I also wouldn't "never". That's too absolute a
statement.
Dan
> ----------
> From: Paul Allton[SMTP:[EMAIL PROTECTED]]
> Reply To: Paul Allton
> Sent: Tuesday, October 26, 1999 3:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: custom tags, xmlc, scalability (was: when to use bean..)
>
> ----- Original Message -----
> From: Brien Voorhees <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, October 26, 1999 6:27 PM
> Subject: Re: custom tags, xmlc, scalability (was: when to use bean..)
>
>
> > ----- Original Message -----
> > From: Eduardo Pelegri-Llopart <[EMAIL PROTECTED]>
> > Subject: custom tags, xmlc, scalability (was: when to use bean..)
> >
> >
> > > Custom tags are very flexible; most of the standard tags of JSP 1.0
> can
> > > be described as custom tags, and many JSP vendors are providing their
> > > own tag libraries to help their customers. The APM team is using tag
> > > libraries in several places, for example there is one set that
> provides
> > > integration with the EJB objects, and another that is used to
> construct
> > > the MVC controller. I am currently using a few simple tags to write
> the
> > > conformance tests for JSP implementations.
> >
> > I'd be very interested to see some of those tags/tag-libraries,
> > especially the EJB ones. Any idea when/if those will be released to the
> > public? (what does APM stand for, anyway? Application Programming
> Model?)
> > I'm going to be integrating with EJB's in the web app I'm developing
> and
> > I haven't decided whether it makes sense to connect to the EJB's within
> the
> > JSP page (with or without custom tags) or if the EJB's should be set up
> by
> a
> > servlet and merely read by the JSP. RemoteException handling seems like
> it
> > will be a pain within the JSP, as well.
> >
>
> To my mind EJB's should never be accessed directly from JSP or serlvet.
> If
> you want to build something thats scalable and channel independent then
> JSP
> should handle only basic presentation layer stuff, anything else - EJB's,
> business logic etc should be handled elsewhere.
>
> IMHO JSP should just call getters and setters on a class (or bean) that
> sits
> behind the JSP. That bean or class should then invoke other classes or
> EJB's as required.
>
> ==========================================================================
> =
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
