Mark,
The servlet - bean - JSP approach is a clean and scalable way to handle your
needs. You might find it useful to genericize your beans as well if you
make a lot of different SQL calls for different data combinations. This
helps genericize the JSP that presents the data.
I'm not a big fan of putting JDBC logic directly in my JSP.
Dan
--
Daniel Kirkdorffer
Sr. Consultant, Syllogistics LLC
Web: http://www.syllogistics.com/
Email: [EMAIL PROTECTED]
> ----------
> From: Mark Hughes[SMTP:[EMAIL PROTECTED]]
> Reply To: Mark Hughes
> Sent: Thursday, March 04, 1999 7:42 AM
> To: [EMAIL PROTECTED]
> Subject: Resultset through JSP / bean
>
> Hi,
>
> We're looking at implementing some sites based on the JSP / Bean model.
> Whilst single properties and arrays are straight forward enough,
> one common requirement of most of these pages is to represent the
> resultset from a SQL query.
>
> We're keen to avoid Java code in the HTML template - how have people
> gone about implemeting this with the bean model?
>
> Any ideas / comments more than welcome :-)
>
> Thanks,
> Mark.
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff JSP-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 JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
