Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 33363 invoked by uid 500); 12 May 2003 09:12:03 -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 33343 invoked from network); 12 May 2003 09:12:02 -0000 Received: from unknown (HELO mail.dff.local) (62.159.19.130) by daedalus.apache.org with SMTP; 12 May 2003 09:12:02 -0000 Received: from altair.dff.local ([172.16.2.8] helo=dff.st) by mail.dff.local with esmtp (Exim 3.35 #1) id 19F9Ly-0005Yh-00 for cocoon-dev@xml.apache.org; Mon, 12 May 2003 11:12:14 +0200 Message-ID: <3EBF65FD.10206@dff.st> Date: Mon, 12 May 2003 11:14:37 +0200 From: Torsten Curdt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: _esql_connection.connection should be public References: <3EBF4C7C.B5BA85B8@wincor-nixdorf.com> In-Reply-To: <3EBF4C7C.B5BA85B8@wincor-nixdorf.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 Enke, Michael wrote: > Hi group, > after updating to M1 I found that in Cocoon2EsqlConnection > the connection variable is private in 2.1 but was public in 2.0. > > I propose to set this field again to public access. Hm... what about changing getConnection() from protected to public? ...not very happy about this either but... > I heavily use method calls from inside of xsp pages to methods which need > a DB connection. I pass the _esql_connection.connection to this methods. > But with private access this is no longer possible. > Why this was changed to private? Because you shouldn't use the ESQL classes directly ;-) cheers -- Torsten