Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Subject: Re: [2.1]Lastest CVS build broken (EsqlConnection)
From: Torsten Curdt <tcurdt@dff.st>
To: cocoon-dev@xml.apache.org
In-Reply-To: <200210201240.37953.agallardo@agsoftware.dnsalias.com>
References: <200210200825.35573.agallardo@agsoftware.dnsalias.com>
	<200210200929.09700.agallardo@agsoftware.dnsalias.com>
	<200210201749.04636.tcurdt@dff.st>
	<200210201240.37953.agallardo@agsoftware.dnsalias.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 20 Oct 2002 23:44:41 +0200
Message-Id: <1035150281.1871.19.camel@defiant.dff.local>
Mime-Version: 1.0

On Sun, 2002-10-20 at 20:40, Antonio Gallardo Rivera wrote:
> Thanks for your prompt request.
> 
> I checked it. The build.sh recongnize my 1.4 VM. It select 1.4 JVM. But I 
> think there is a problem inside the database-block. I think this is not a 
> question about the java version of the compiler:

I am pretty sure it is :)

Have a look at the original source code:

http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/blocks/databases/java/org/apache/cocoon/components/language/markup/xsp/EsqlConnection.java

You will see the @JDBC3_START@ and @JDBC3_END@ markers. They are used by
the build system to uncomment the necessary implementations depending on
the JVM version. So I guess the transition into the database block broke
this mechanism.

This needs to be fixed...

So you have 4 options:
1) you fix it (and provide a patch)
2) you uncomment the code by yourself
3) you use JDK 1.3
4) wait for someone else to do it

...I'd prefer 1) ;-)

cheers
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org