At 01:39 AM 23/02/2004 +0900, you wrote:

>Hello all,
>
>I try to connect Firebird database with Jaybird JDBC driver.
>Even though loading JDBC driver in web.xml, below error is encountered.
>
> Could not get the datasource
>org.apache.avalon.excalibur.datasource.NoValidConnectionException:
>No valid JdbcConnection class available
>
>I use cocoon 2.0.4, Jaybird 1.0.1 and Firebird 1.0.3 and I try Firebird
>1.5 RC9 and
>Jyabird 1.5 Beta 3.
>
>It is ok that you tell me your environment work fine.
>
>Please let me know if you know why.

As I explained in firebird-java, the ESQL guru is Ann Harrison, so I'm
copying this here in the hope that Ann will catch it and put the story
straight for us.

As far as I understand it, you can't combine ESQL with an external
connectivity layer at all. The gpre pre-compiler converts the ESQL blocks
into host-language source code. Currently gpre is only available for C and
Cobol, I think.

You would need to write your own version of gpre in Java that implements
the ESQL equivalents to the API functions that Jaybird maps to JDBC, i.e.
translates the ESQL into something that Java can compile to pass the
correct C structures to the server. The "gain" from doing that hardly
justifies the effort.

For a stand-alone embedded application it's simpler to abandon ESQL and
write an ordinary DSQL client/server application that utilises the Jaybird
classes. On Windows your Jaybird app can use the embedded server, on Linux
it can use Classic.

/heLen