Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 54684 invoked by uid 500); 5 Mar 2003 18:10:30 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 54628 invoked from network); 5 Mar 2003 18:10:28 -0000 Received: from fo1.kc.aoindustries.com (HELO www1.kc.aoindustries.com) (209.15.201.17) by daedalus.apache.org with SMTP; 5 Mar 2003 18:10:28 -0000 Received: from apache.org ([66.208.12.130]) (authenticated) by www1.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id h25IAV406665 for ; Wed, 5 Mar 2003 12:10:32 -0600 Message-ID: <3E663D95.3050406@apache.org> Date: Wed, 05 Mar 2003 13:10:29 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Presenting the Proxy Based DataSource References: <3E660D05.8010400@apache.org> <3E6614F2.2060200@anyware-tech.com> <3E6615C4.1020102@apache.org> <3E6627C7.9050705@anyware-tech.com> <3E662A59.7030707@apache.org> <3E663C77.7030502@anyware-tech.com> In-Reply-To: <3E663C77.7030502@anyware-tech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sylvain Wallez wrote: > Berin Loritsch wrote: > >> Sylvain Wallez wrote: >> >>> Berin Loritsch wrote: >>> >>> So it seems to me that a simple way to avoid this JDBC mess (at least >>> in Cocoon) would be for ESQLConnection to _hold_ a Connection instead >>> of _extending_ it. >> >> >> >> For ESQLConnection, definitely. For Excalibur DataSource, it extends >> the close() and isClosed() methods to provide pooling. Any other >> methods that we extend are taken care of in the proxy object so we can >> still work with JDK 1.3 and JDK 1.4. At least that is the theory. > > > > Since close() and isClosed() are JDBC2, maybe compiling the full JDBC3 > version with JDK 1.4 and use it with JDK 1.3 may work ? As I mentioned before, we have already done that. For some reason, Cocoon complained about invalid clss files and such. Can you confirm if my changes work on JDK 1.3? I think it is the cleanest solution and allows people with JDK 1.3 to build the library and it will still work with JDK 1.4. Cocoon is the problem application for this package, which is why I wanted you guys to verify it.