While Troy's question is being discussed on the cayenne-user, I think
it raises an issue we must address in the upcoming beta.
The exception below is the most often quoted error that new users get.
At least 3 people mailed me privately about this last month. Reasons
ranged from typos in database URLs to JDBC drivers not included in the
CLASSPATH, i.e all kinds of environment configuration issues, not
directly related to Cayenne. Cayenne's fault here is insufficient error
reporting. While this could be fixed by turning on logging, such
solution is not obvious and the exceptions must be self explanatory by
definition.
My solution to that would be to create a new method "String
ConfigStatus.describeFailures()" and add the output of this method to
the message of the thrown exception. Before I do that, I wanted to post
to this list, since Holger was lately working on configuration logging
issues and I don't want to interfere with his work.
Andrus
On Monday, March 31, 2003, at 07:26 PM, Troy McKinnon wrote:
> ERROR Configuration: Error initializing shared Configuration
> org.objectstyle.cayenne.ConfigException:
> [org.objectstyle.cayenne.conf.DefaultConfiguration] : Failed to load
> domain and/or its maps/nodes.
> at
> org.objectstyle.cayenne.conf.RuntimeLoadDelegate.finishedLoading(Runtim
> eLoadDelegate.java:420)
> at
> org.objectstyle.cayenne.conf.ConfigLoader.loadDomains(ConfigLoader.java
> :125)
> at
> org.objectstyle.cayenne.conf.Configuration.init(Configuration.java:278)
> at
> org.objectstyle.cayenne.conf.Configuration.initSharedConfig(Configurati
> on.java:228)
> at
> org.objectstyle.cayenne.conf.Configuration.initSharedConfig(Configurati
> on.java:219)
> at
> org.objectstyle.cayenne.conf.Configuration.initSharedConfig(Configurati
> on.java:197)
> at
> org.objectstyle.cayenne.conf.Configuration.getSharedConfig(Configuratio
> n.java:168)
> at
> org.objectstyle.cayenne.access.DataContext.createDataContext(DataContex
> t.java:155)
This archive was generated by hypermail 2.0.0 : Mon Mar 31 2003 - 20:47:50 EST