You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Antonio Gallardo Rivera <ag...@agsoftware.dnsalias.com> on 2002/10/20 20:40:37 UTC
Re: [2.1]Lastest CVS build broken (EsqlConnection)
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:
/xml-cocoon2/build/cocoon/blocks/databases/src/org/apache/cocoon/components/language/markup/xsp/EsqlConnection.java:66:
org.apache.cocoon.components.language.markup.xsp.EsqlConnection should be
declared abstract; it does not define setHoldability(int) in
org.apache.cocoon.components.language.markup.xsp.EsqlConnection
public class EsqlConnection implements Connection {
^
1 error
As you can see there is an error that said:
EsqlConnection should be declared abstract; it does not define
setHoldability(int) in
org.apache.cocoon.components.language.markup.xsp.EsqlConnection
Regards,
Antonio Gallardo
El Domingo, 20 de Octubre de 2002 09:49, Torsten Curdt escribió:
> > > ...are you using jdk 1.4?
> >
> > Yes, 1.4.1
>
> ...there you go - your ant is trying to compile the class assuming you have
> a jdk 1.2 - 1.3. You need to tell the build system you are using jdk 1.4
> due to some JDBC API changes from 1.3 to 1.4.
>
> ...but AFAIR Carsten already put a check into the build.xml :-/ ?
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (Esql.xsl not found)
Posted by Antonio Gallardo Rivera <ag...@agsoftware.dnsalias.com>.
I made 2). The easiest way. To build the sources. It helps :-D. It compiles,
but now I am now getting the error:
org.apache.cocoon.ProcessingException: Exception during processing of
cocoon://ags-checkuser?password=mypass&name=myname:
org.apache.cocoon.ProcessingException: Could not transform
resource://org/apache/cocoon/components/language/markup/xsp/java/esql.xsl:
org.apache.avalon.excalibur.xml.xslt.XSLTProcessorException: Exception in
creating Transform Handler
I also check the generated jars for the file esql.xsl and the file was not in:
cocoon-2.1-dev.jar
cocoon-databases-block.jar
That means in the build.sh there is a error.
Regards,
Antonio Gallardo
El Domingo, 20 de Octubre de 2002 15:44, Torsten Curdt escribió:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Antonio Gallardo Rivera <ag...@agsoftware.dnsalias.com>.
El Domingo, 20 de Octubre de 2002 19:38, Vadim Gritsenko escribió:
> Torsten Curdt wrote:
> >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:
>
> Have you done "build clean" ( == rm -rf build) recently?
Yes, Vadim.
Antonio
>
> Vadim
>
> >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/or
> >g/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
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Vadim Gritsenko <va...@verizon.net>.
Torsten Curdt wrote:
>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:
>>
Have you done "build clean" ( == rm -rf build) recently?
Vadim
>>
>>
>
>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
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 21.Oct.2002 -- 10:07 AM, Antonio Gallardo Rivera wrote:
> I did a total new cocoon CVS 2.1
>
> It compiles, but now the problem is that the esql.xsl stylesheet is not
> present into any generated .jar. I guess it must be automatically included at
> build time into any of these files:
Fixed. Please update.
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Antonio Gallardo Rivera <ag...@agsoftware.dnsalias.com>.
I did a total new cocoon CVS 2.1
It compiles, but now the problem is that the esql.xsl stylesheet is not
present into any generated .jar. I guess it must be automatically included at
build time into any of these files:
cocoon-databases-block.jar
cocoon-2.1-dev.jar
But this is not. I can put it manually the esql.xsl to make it work, but this
is an error at buid time. This does not matter how many times you run the
build or if you use only build.sh or any combinations with the webapp.
My build command is:
***************************************
./build.sh -Dinclude.webapp.libs=true -Dinclude.scratchpad.libs=true
installwar
***************************************
The error is clear, it cannot find the esql.xsl to process database tags in
XSP:
*********************************************************************************
org.apache.cocoon.ProcessingException: Exception during processing of
cocoon://my-checkuser?password=mypass&name=myname:
org.apache.cocoon.ProcessingException: Could not transform
resource://org/apache/cocoon/components/language/markup/xsp/java/esql.xsl:
org.apache.avalon.excalibur.xml.xslt.XSLTProcessorException: Exception in
creating Transform Handler
*****************************************************************************
Regards,
Antonio Gallardo
El Lunes, 21 de Octubre de 2002 02:25, Christian Haul escribió:
> On 21.Oct.2002 -- 09:38 AM, Christian Haul wrote:
> > On 20.Oct.2002 -- 11:44 PM, Torsten Curdt wrote:
> > > 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
> >
> > OK, looks like it's my fault, although my local repository does the
> > commenting / uncommenting right (sun j2sdk 1.4.1 and blackdown
> > 1.3.1_02FCS on debian linux). Must have missed a file during cvs
> > update.... will look into this.
>
> I did a fresh checkout and could not reproduce any problem related to
> jdbc3 / jdk 1.4. Antonio, please delete your cvs snapshot and try
> again with a fresh one.
>
> Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 21.Oct.2002 -- 09:38 AM, Christian Haul wrote:
> On 20.Oct.2002 -- 11:44 PM, Torsten Curdt wrote:
> > 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
>
> OK, looks like it's my fault, although my local repository does the
> commenting / uncommenting right (sun j2sdk 1.4.1 and blackdown
> 1.3.1_02FCS on debian linux). Must have missed a file during cvs
> update.... will look into this.
I did a fresh checkout and could not reproduce any problem related to
jdbc3 / jdk 1.4. Antonio, please delete your cvs snapshot and try
again with a fresh one.
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 20.Oct.2002 -- 11:44 PM, Torsten Curdt wrote:
> 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
OK, looks like it's my fault, although my local repository does the
commenting / uncommenting right (sun j2sdk 1.4.1 and blackdown
1.3.1_02FCS on debian linux). Must have missed a file during cvs
update.... will look into this.
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [2.1]Lastest CVS build broken (EsqlConnection)
Posted by Torsten Curdt <tc...@dff.st>.
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