cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Gregory" <>
Subject <esql:use-limit-clause>oracle</esql:use-limit-clause>
Date Sat, 28 Feb 2004 13:31:43 GMT
Hi All

I have been looking into the issue of EQSL paging no longer working with
Oracle since upgrading Cocoon from 2.0.3 to 2.1.4 and although I can't
see any direct reason in the code for this problem I have noticed that
if I use jdbc as the limit clause instead of our default setting of auto
the paging seems to work again and the <esql:more-results> is output.

Can anyone (hopefully Chris) expand on this issue and advise on any
further suggestions on how to fix this as I would prefer not to have to
visit all our XSP's and change the limit clause setting to be JDBC as we
plan on supporting more than just Oracle sometime in the future.

Is this an Oracle problem or a Cocoon one (as the same code works fine
under 2.0.3) without the change to jdbc.

> > Please could anyone confirm that they are using Oracle with ESQL on 
> > Cocoon 2.1+ with the <esql:more-results> tag working??
> >  Thanks in advance for any input.  
> There have been some refactorings of the code that determines the
> number of rows in a resultset. These are most likely the cause of your
> troubles :-|
> Please have a look at 
> org.apache.cocoon.components.language.markup.xsp.OracleQuery 
> and super 
> classes. Maybe you can give some advice how to adjust it to your needs
> or point out different cases we need to distinguish.
> 	Chris.

Futher Details to my initial problem are as follows:-
<esql:more-results> no longer output! 
Hi people
I have been using Cocoon since version 2.0.3 and have used the ESQL
logicsheet from within XSP and all was fine until I recently upgraded to
Cocoon version 2.1.3. Since the upgrade the esql queries etc still work
and produce results in the page size I specify but the esql node
<esql:more-results> is no longer output. The paging I specify still
seems to work and 10 rows are skipped if I use the <esql:skip-rows> node
and I know there are lots more results available in the result set. If I
ignore the more-results tag and hard code a link to the next results
this also works but I really need to know when there are more results
available and not.
We are using Cocoon in a production environment so any help to resolve
this matter is gratefully received. I can degrade back to version 2.0.3
but following a bug where resources were being lost when the esql error
block was entered I would really like to keep to the current versions.
Thanks in advance for any help
Environment Details:-
Tomcat 5.0.18 (also fails on 4.1.24)
Cocoon 2.1.3 (also fails on 2.1.4)
Oracle 9
Windows 2000 (also fails on XP)
JDK 1.4.1
JDBC driver ojdbc14.jar


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message