Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D0B83ECAE for ; Mon, 11 Feb 2013 16:15:15 +0000 (UTC) Received: (qmail 14255 invoked by uid 500); 11 Feb 2013 16:15:15 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 13904 invoked by uid 500); 11 Feb 2013 16:15:14 -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 13833 invoked by uid 99); 11 Feb 2013 16:15:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 16:15:13 +0000 Date: Mon, 11 Feb 2013 16:15:13 +0000 (UTC) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (OPENJPA-2332) Update message when unable to resolve datasource configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Kevin Sutter created OPENJPA-2332: ------------------------------------- Summary: Update message when unable to resolve datasource configuration Key: OPENJPA-2332 URL: https://issues.apache.org/jira/browse/OPENJPA-2332 Project: OpenJPA Issue Type: Improvement Components: diagnostics, jdbc Affects Versions: 2.3.0, 2.2.2, 2.2.1.1 Reporter: Kevin Sutter Assignee: Kevin Sutter This error message does not give sufficient information to debug the situation. Users don't know how or why they got to this point in the processing: no-driver: A JDBC Driver or DataSource class name must be specified in the \ ConnectionDriverName property. Available properties in configuration \ are "{0}". Without getting too wordy for a single message, I'm planning to update this message as follows. I also plan to add some additional Trace points to help with debugging the issue. no-driver: Now relying on persistence.xml properties to resolve the datasource. \ A JDBC Driver or DataSource class name must be specified in the \ openjpa.ConnectionDriverName or javax.persistence.jdbc.driver property. \ Available properties in the configuration are "{0}". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira