tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kris Schneider <>
Subject Re: Different generation of JSTL sql:query
Date Wed, 07 Jul 2004 12:57:30 GMT
Can you give an example of how you're using the tags and indicate which has code
generated directly into _jspService and which has code generated into its own
method? On a realted note, if you want better control over exception handling
in your pages, you can try using the <c:catch> tag:

<c:catch var="exc">
  <sql:query ...>
<c:if test="${exc}">

Quoting "Geesken, Edmund" <>:

> Hi,
> I have some problems with the JSTL taglibrary 1.1. Some of my JSPs which are
> using the sql:query tag are generated in a different way. For some of them
> the generation of the sql:query tag is directly included
> into the service method body of the JSP and for others a separate method is
> generated and called from within the service method. This would make no
> difference if the different generations would react the same way. But for
> these JSPs where the sql:query tag is generated directly into the service
> method body an exception during the excecution just interupts the execution
> of the JSP, the exception is written into the server system.out, the JPS is
> displayed with no information about the exception. For the JSPs where the
> sql:query tag is separated into a private method, an exception in this
> methods leads to an exception which is displayed on the screen, which is
> definitly what i expected.
> Is there a way to change the way the JSPs are generated? Can anyone explain
> me why these JSPs are generated in two different ways?
> Regards
> Edmund
> Environment
> JBoss 3.2.3
> JDK 1.4.2
> JSTL 1.1
> Struts 1.1

Kris Schneider <>
D.O.Tech       <>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message