From dev-return-6505-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Thu Oct 18 14:33:58 2007 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 16187 invoked from network); 18 Oct 2007 14:33:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Oct 2007 14:33:58 -0000 Received: (qmail 73833 invoked by uid 500); 18 Oct 2007 14:33:45 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 73798 invoked by uid 500); 18 Oct 2007 14:33:45 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 73788 invoked by uid 99); 18 Oct 2007 14:33:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2007 07:33:45 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates 209.85.198.187 as permitted sender) Received: from [209.85.198.187] (HELO rv-out-0910.google.com) (209.85.198.187) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2007 14:33:49 +0000 Received: by rv-out-0910.google.com with SMTP id k20so192372rvb for ; Thu, 18 Oct 2007 07:33:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=nys9ep1h3fzeCOIszEwkCLlwx531NzftgKowRMvhi1A=; b=I1R8xGwZYytFKj224VSfwyKUfBRiU1Nipw0eE7leTYWoPTQCccO1+C7IreAF8vBVNYFpDkTdC75KhKRYlnChS5u3I5ghQyWe0smTCNOSmI6wLq1iOrOMpCDEIgRxZE1SlS3Gj61TD9Z4lOFFW0gbu/3n8UAV76zPCSJdQemhnmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=CdddnDM/7stIivG2AYVg8lfcqbUMP+9+IFpe6H7cf6+4GqhgSA0oKpyk63mNfvkJ7dyShqNUK4zHGHaQ8hbbw7ONn4dHgk+qWse8Z7BNomDFZqs7KVZjj/7e9hYN3qK7E+X/FnoXHqMlrv52p9YwhYGmqOTVc+OqkQOEuZGnAAA= Received: by 10.115.32.1 with SMTP id k1mr722255waj.1192718008338; Thu, 18 Oct 2007 07:33:28 -0700 (PDT) Received: by 10.114.75.15 with HTTP; Thu, 18 Oct 2007 07:33:28 -0700 (PDT) Message-ID: <89c0c52c0710180733u22377863o7ce9c1b61da84614@mail.gmail.com> Date: Thu, 18 Oct 2007 09:33:28 -0500 From: "Kevin Sutter" To: dev@openjpa.apache.org Subject: Change "connecting to dictionary" message from Info to Trace? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1706_13055770.1192718008331" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_1706_13055770.1192718008331 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Currently, we issue the following message as an Info message whenever we don't have enough configuration data to determine the proper dictionary to use. The message seems to be overkill, especially when running within a Container environment and the use of and elements. It's very confusing to our Application Server customers when they are using the JPA-defined constructs for accessing the jta and non-jta datasources. The message makes it sound like they are missing some configuration, where in reality they have done everything right and we just need to query the datasource to determine the right dictionary to use. I can kind of understand it when using the openjpa.Connection* properties to define your datasources, but even then, do we need to log this as an Info message? connecting-for-dictionary: OpenJPA will now connect to the database to attempt \ to determine what type of database dictionary to use. To prevent this \ connection in the future, set your openjpa.jdbc.DBDictionary \ configuration property to the appropriate value for your database (see \ the documentation for available values). Would there be any backlash if we changed this message to a Trace level message instead? Thanks, Kevin ------=_Part_1706_13055770.1192718008331--