You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/02/12 17:03:13 UTC
[jira] [Commented] (OPENJPA-2332) Update message when unable to
resolve datasource configuration
[ https://issues.apache.org/jira/browse/OPENJPA-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576722#comment-13576722 ]
ASF subversion and git services commented on OPENJPA-2332:
----------------------------------------------------------
Commit 1445220 from kwsutter
[ https://svn.apache.org/r1445220 ]
OPENJPA-2332. Updated the "no-driver" message and added a couple of additional Trace statements to help with debugging Datasource configuration issues.
> 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