Hi all,
I did some digging and discovered a solution to the interaction problems
with Cocoon, JDBC and JRE1.4.0.
The problem lies in the version of Avalon-Excalibur currently packaged
with Cocoon both in release and CVS. The first thing I tried was moving
to the bleeding edge 2.1-dev from CVS but I still had the same JDBC
problems, namely:
org.apache.avalon.excalibur.datasource.NoValidConnectionException: No
valid JdbcConnection class available
So then I tried rebuilding the entire latest Avalon-Excalibur package
from CVS. However, Avalon-Excalibur is in a state of flux (according
to the project webpage) and I ran into some compilation problems
very early on in the build.
However, I was able to build the Avalon Framework and Logkit from CVS.
That was enough to let me build the Avalon-Excalibur-Datasource
package (Datasource is the part of Excalibur that is causing grief
here). I then took the Excalibur jar file currently in Cocoon's CVS
(avalon-excalibur-20020506.jar), replaced the Datasource class files
with those that I just built, rebundled the excalibur jar file and
presto! JDBC works with cocoon and ESQL is working again.
My new excalibur jar file is 343k and _should_ work as a drop-in
replacement for the excalibur jar shipped with 2.0.2+ but I can't
regress back to test with 2.0.2 so I'm leaving that as an exercise for
the reader. The jar is a little large to send to the mailing list
but I'll gladly email a copy to the first 10 people that write me :)
Preferably, a Cocoon maintainer will verify that this is a sensible
thing to do and will update the CVS HEAD accordingly.
Cheers, Jonathan
On Mon, Jun 03, 2002 at 11:26:24PM +0200, Michael Mangeng wrote:
> Hi
>
> Yes... i would like to know that too.
> After several frustrating days i�ve discovered that i simply have to use
> jdk1.3.1... But thats no solution... only a 'workaround'...
>
> Such things would be _VERY_ important to be noted somewhere in the docus and
> not only, very good hidden, somewhere in the mailing list archives..
>
> greetings
> mike
> ----- Original Message -----
> From: "Jonathan Layes" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, June 03, 2002 4:23 PM
> Subject: mm.mysql-2.0.14 + JRE1.4.0 + Cocoon2.0.2 problem resolution?
>
>
> > Hi all,
> >
> > I have found a few snippits in the mailing list archives that indicate
> > that mm.mysql-2.0.14 + JRE1.4.0 + Cocoon2.0.2 is a bad combination.
> >
> > Has anyone figured out why they are not working together? Is there
> > a known solution? FWIW, I'm getting the ubiquitous message:
> >
> > org.apache.avalon.excalibur.datasource.NoValidConnectionException: No
> valid JdbcConnection class available
> >
> > which isn't very informative, unfortunately.
> >
> > Thanks, Jonathan
> >
> >
> > ---------------------------------------------------------------------
> > Please check that your question has not already been answered in the
> > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
> >
> >
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
