Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 7265 invoked from network); 9 Apr 2005 14:31:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Apr 2005 14:31:46 -0000 Received: (qmail 45012 invoked by uid 500); 9 Apr 2005 14:31:41 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 44959 invoked by uid 500); 9 Apr 2005 14:31:41 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 44945 invoked by uid 99); 9 Apr 2005 14:31:41 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jc.textor@gmx.de designates 213.165.64.20 as permitted sender) Received: from pop.gmx.net (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 09 Apr 2005 07:31:39 -0700 Received: (qmail invoked by alias); 09 Apr 2005 14:31:36 -0000 Received: from i3ED6165E.versanet.de (EHLO [192.168.0.23]) [62.214.22.94] by mail.gmx.net (mp002) with SMTP; 09 Apr 2005 16:31:36 +0200 X-Authenticated: #2236490 Message-ID: <4257E748.4000907@gmx.de> Date: Sat, 09 Apr 2005 16:31:36 +0200 From: Johannes Textor User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: Cocoon, Hibernate and HSQL References: <425771DC.7060604@apache.org> In-Reply-To: <425771DC.7060604@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Leszek Gawron schrieb: > You can put all your database configuration data in hibernate.cfg.xml > and it will work just fine. No need to use cocoon connection pools. Although this is slightly offtopic, I'd like to give my 2c on this (since it would mean that my poor tutorial would be useless ;) ): The Hibernate builtin connection pool is for testing purposes only. It might work on some databases, but I definately saw it break on MySQL when leaving it running overnight. AFAIK, Hibernate is designed to work with an extern implementation of connection pooling, and supplies its own pooling just to get people started quicker. One more reason to use cocoon connection pooling might be that you might find it a little nicer to have one central place to put your database credentials and have only one pooling implementation running in your webapp. The cocoon builtin connection pool was the first thing that came into my mind when I implemented this. As far as I am aware of it, most people prefer using Swing and C3PO instead, but few stick around with the Hibernate builtin pool, at least not when putting the app into production. Thoughts ? Regards, Johannes --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org