You should commit or rollback BEFORE the JSP page. The JSP page is only
your display, all logic should have been performed before going to the JSP
page. Thus you have seperation of business logic and presentation. (i.e.
your JSP page should only show the results of committing or rolling back, it
should not actually be performing those operations)
I fully agree that SQL and CONNECTION tags don't make any sense in a JSP
page. Looping, conditional constructs and the like (only for display
purposes, not for actually coding logic) would be good standard tags.
The rule would be: do most if not all JSP applications need these tags?
For database tags, I think the answer to that question is definitely NO!
-taylor
----- Original Message -----
From: Foster Bob <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 02, 1999 12:28 PM
Subject: Re: [Fwd: Proposal for standardized tags]
> Michael Hu wrote:
>
> >Connection attributes don't belong in the query tag, definitely. I would
> >argue connections (and query select statements) also don't belong in JSP
> >pages. Sorta orthogonal.
>
> Then how do you propose to implement commit and rollback in JSP pages?
>
> Bob Foster
> Symantec Internet Tools http://www.visualcafe.com/
>
>
===========================================================================
> 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
