Curious. It certainly seems to be an issue with the app server, although I suppose it
could also be a misinterpretation of the spec on my part.
I know that the JSP JSRs have gone back and forth over time on the meaning of the id
attribute; sadly I don't know all the details since JSRs are a closed forum. You
might want to check the Resin website for any outstanding issues.
Steve Philp wrote on 8/8/01 8:24 am:
>Morgan Delagrange wrote:
>>
>> The syntax of DBTags
>definitely does not support
>multiple queries per
>statement tag (i.e. your
>pseudo-code example will
>not work.)
>>
>> It's curious that using
>separate statement tags did
>not work however. Could you
>send pseudo code for that
>usage?
>
>I'm not the original poster,
>but I'm experiencing similar
>problems with all pages that
>use multiple statements.
>The pages work correctly
>with Resin 1.2.7, but fail on
>Resin 2.0.1. The dbtags
>library I'm using is dated
>20010508.
>
>The pages look like this:
>
> <sql:connection
>id='conn'>
>
><sql:jndiName>java:comp/e
>nv/jdbc/dbname</sql:jndiN
>ame>
> </sql:connection>
>
> <sql:statement id='foo'
>conn='conn'>
> <sql:query>
> select * from
>tablename_1
> </sql:query>
> <sql:resultSet id='rs'>
> <sql:getColumn
>position='1'/><br><sql:getC
>olumn position='2'/><br>
> </sql:resultSet>
> </sql:statement>
>
> <sql:statement id='bar'
>conn='conn'>
> <sql:query>
> select * from
>tablename_2
> </sql:query>
> <sql:resultSet id='rs2'>
> <sql:getColumn
>position='1'/><br><sql:getC
>olumn position='2'/><br>
> </sql:resultSet>
> </sql:statement>
>
> <sql:closeConnection
>conn='conn'/>
>
>The pages respond with a
>NullPointerException when
>run under the newer Resin. If
>I remove _either_ of the
>queries, the page displays
>correctly. It doesn't matter
>which I remove... just have to
>leave a single
><sql:statement>.
>
>Thanks,
>
>--
>Steve Philp
>Advance Packaging
>Corporation
>[EMAIL PROTECTED]
