Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Delivered-To: moderator for cocoon-dev@xml.apache.org Received: (qmail 80459 invoked from network); 6 Jan 2001 16:49:58 -0000 Received: from fmailg2.svr.pol.co.uk (195.92.195.184) by h31.sny.collab.net with SMTP; 6 Jan 2001 16:49:58 -0000 Received: from [195.92.193.215] (helo=mail12.svr.pol.co.uk) by fmailg2.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14EwXW-0007FF-00 for cocoon-dev@xml.apache.org; Sat, 06 Jan 2001 16:49:58 +0000 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by mail12.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14EwXS-0004MW-00 for cocoon-dev@xml.apache.org; Sat, 06 Jan 2001 16:49:54 +0000 Received: from modem-102.wisconsin.dialup.pol.co.uk ([62.137.99.102] helo=hydrogen) by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14EwXR-0001GD-00 for cocoon-dev@xml.apache.org; Sat, 06 Jan 2001 16:49:53 +0000 Received: from paulr by hydrogen with local (Exim 3.20 #1 (Debian)) id 14EwZt-0006WF-00 for ; Sat, 06 Jan 2001 16:52:25 +0000 Date: Sat, 6 Jan 2001 16:52:25 +0000 From: Paul Russell To: cocoon-dev@xml.apache.org Subject: Re: [C2] Force-Load and DataSources Message-ID: <20010106165224.O682@hydrogen.internal.luminas.co.uk> Reply-To: Paul Russell References: <3A574A41.87759BAC@infoplanning.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <3A574A41.87759BAC@infoplanning.com>; from bloritsch@infoplanning.com on Sat, Jan 06, 2001 at 11:39:29AM -0500 Sender: Paul Russell X-BadReturnPath: paulr@hydrogen.internal.luminas.co.uk rewritten as prussell@apache.org using "Reply-To" header X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N * Berin Loritsch (bloritsch@infoplanning.com) wrote : > I was thinking, we should probably change the name of the > init parameter "force-load" to "drivers" so that it is > more clear that this is the perfect place to load the > JDBC Driver in memory. Instead of repeating the Driver > setting and reloading the same class in multiple locations, > I was thinking that the JDBC drivers should be loaded > in the init-parameter since the functionality is the same, > and it is only done once per driver. That way, connections > only need the dburl, the user, and the password. Hmm. However, I tend to stick to the rule that we should use names that say what they do. 'force-load' does exactly what it says on the tin. The fact that the drivers happen to register themselves in their static initializers (or constructors) is a side effect, rather than the aim. I can see what you're trying to do, but I'm not keen on the implications for those wishing to force-load non-driver classes. Maybe we could make them an alias, so both 'force-load' and 'driver' force load a class. Thoughts? Paul. -- Paul Russell Email: paul@luminas.co.uk Technical Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order. Web: www.luminas.co.uk