|
Cyril,
You
probably should set up a datasource, using the ODBC data manager. That's what
the logs part 'jdbc:odbc:logs' is referring to in your <dburl> tag. Use
the data source manager to create a data source, 'logs' that refers to your
access database 'C:....\JAVA\JDBC\logs.mdb'.
When
you execute, check the cocoon logs, TOMCAT\webapps\cocoon\web-inf\logs to see
what problems are occuring, if any! Also enable tracing in the ODBC data source
manager to see if your queries are being passed to ODBC.
Perry
Hi Perry,
I've tried with // instead of
/ ,it isn't better...
Anyway, I've configurated with esql
and pool.
the cocoon.xconf looks like
this:
<jdbc name="pool">
<pool-controller min="5" max="10"/>
<dburl>jdbc:odbc:logs</dburl> (with odbc, we don't need
to write the complete url, right??)
<user></user>
<password></password>
</jdbc>
and I didn't forget to load the driver in web.xml...
My file base1.xsp is this one, as simple as
possible, just to test the connection
<?xml version="1.0"
encoding="iso-8859-1"?>
<xsp:page
language="java"
xmlns:xsp="http://apache.org/xsp">
xmlns:esql="http://apache.org/cocoon/SQL/v2">
<doc>
<esql:connection>
<esql:pool>pool</esql:pool>
</esql:connection>
</doc>
</xsp:page>
To my great surprise, when I execute this file, I obtain:
<doc xmlns:xsp="http://apache.org/xsp">
<connection>
<pool>pool</pool>
</connection>
</doc>
I think, it's not normal...I should not see the connection
element... I think I have to change the line
<dburl>jdbc:odbc:logs</dburl> but I don't know really how to
do...
regards,
Cyril.
----- Original Message -----
Sent: Thursday, May 16, 2002 12:47
AM
Subject: RE: Cocoon 2 + Access
Hi
Cyril,
In
theory it should work, as it's just some Java code, similar to that produced
by ESQL. The disadvantage, is that you don't have any error checking or
logging to fall back on when situations like this occur, and ESQL would
provide that.
Anyway, the only obvious thing that I can see, is to put \\'s in your connection string,
e.g:
("jdbc:odbc:localhost:8080/c:\\Mes_documents\\JAVA\\JDBC\\logs");
Also turn on ODBC tracing and see if any other information is logged,
to help you resolve the problem.
Perry
Hy!
I would like to
know if it is an
obligation to use ESQL and the connection pool provided by Cocoon2 to
connect to a database.
By example, isn't it possible
just to write the following code, by which a simply connection should be
executed with the 'logs' database?
I've tried it and it doesn't
work but I don't know if there's an error on the code or if anyway, it
could never run.
Some of you can help me,
please?
Thanks in advance,
Cyril.
<xsp:structure>
<xsp:include>java.sql*</xsp:include>
</xsp:structure>
<Promotion
auteur="Jules">
<xsp:logic>
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection
conn =
DriverManager.getConnection("jdbc:odbc:localhost:8080/c:\Mes_documents\JAVA\JDBC\logs");
Statement
stmt = conn.createStatement();
ResultSet resultat =
stmt.executeQuery("select * from visit where
userid='cyril'");
</xsp:logic>
<Description>Nous
proposons une réduction de 25%, restreinte à la période de Septembre 20001
à OCtobre 20001</Description>
<row>
<userid><xsp:expr>resultat.getString
(1)</xsp:expr></userid>
<sessionid><xsp:expr>resultat.getString
(2)</xsp:expr></sessionid>
<visitdate><xsp:expr>resultat.getString
(3)</xsp:expr></visitdate>
<referrer><xsp:expr>resultat.getString
(4)</xsp:expr></referrer>
<page><xsp:expr>resultat.getString
(5)</xsp:expr></page>
</row>
</Promotion>
</xsp:page>
|
