Christopher Watson wrote: > > Michael, > Well done, many thanks.
You are welcome ;-) > I've meantime gone back to jdk1.3 ! Now, dare I go back forward again to > jdk1.4 ? (Guess that's my problem to decide!) No other limitations known. > I'm guessing your excellent work is so far a kind of temporary workaround? > Do you see this getting incorporated into a new excalibur jar in cocoon CVS > in the near future? > Would that be someting Berin would do? Yes, he will do this (if he is yet following this thread). He is a committer and can check in. > If not, could you advise me which excalibur sources to edit (CVS - which > branch, or dist, or what) > and also which jars to build excalibur against, and where to get them? I also have the problem with logkit but this is not urgent to me. http://jakarta.apache.org/builds/jakarta-avalon/nightly/2002-03-27/jakarta-avalon-excalibur-src.tar.gz untar, cd jakarta-avalon-excalibur ( cd all/src/scratchpad/org/apache/avalon/excalibur/datasource vi ResourceLimitingJdbcConnectionPool.java line 106 and 156: change JdbcConnection to Jdbc3Connection (both) -> ONLY FOR JDK1.4 <- ) ./build.sh (in jakarta-avalon-excalibur) will do the job, creates excalibur-all.jar Remove in cocoon/WEB-INF/lib avalon-excalibur-4.1.jar and avalon-excalibur-scratchpad-20020212.jar and copy excalibur-all.jar to this location. But: Berin wrote: He will change it in both classes. I don't know what he means with "both classes". I guess he means jakarta-avalon-excalibur/all/src/java/org/apache/avalon/excalibur/datasource/JdbcConnectionPool.java there are also references to JdbcConnection, but changing this to Jdbc3Connection has no effect because "my cocoon configuration" uses ResourceLimitingJdbcConnectionPool instead of JdbcConnectionPool. Happy cocooning, Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
