ok I think I've identified the problem. I am copying the DEV list too.
Tomcat 4.1.12 uses commons-dbcp to implement its connection pool.
There is a mechanism in DBCP to track abandonned objects, so that when a
Connection is closed, the associated Statements *AND* ResultSets are closed
too.
The p
"Sebastian Gil" <[EMAIL PROTECTED]> wrote in message
opriqa1bv0m7k2hg@localhost">news:opriqa1bv0m7k2hg@localhost...
> On Wed, 8 Jan 2003 22:40:37 -, Renaud Bruyeron <[EMAIL PROTECTED]>
> wrote:
>
> >
> > I am facing a weird problem with the SQLTransformer.
> > This happens with cocoon 2.0.4 on
On Wed, 8 Jan 2003 22:40:37 -, Renaud Bruyeron <[EMAIL PROTECTED]>
wrote:
I am facing a weird problem with the SQLTransformer.
This happens with cocoon 2.0.4 on jdk1.3.1 running in Tomcat 4.1.12
Tomcat doesn't contains the required libraries for J2EE datasources by
default. Check
your %C
I am facing a weird problem with the SQLTransformer.
This happens with cocoon 2.0.4 on jdk1.3.1 running in Tomcat 4.1.12
I have a J2EE Datasource defined via Tomcat's JNDI (the db is MySQL) bound
at "java:comp/env/jdbc/Publisher"
I am trying to get cocoon to use that datasource via the
element
