> > org.exolab.castor.jdo.DatabaseNotFoundException: No
> > configuration loaded for database /tmp/testdb -- use the JDO
> > interface to load a configuration for this database
> > at
> > org.exolab.castor.jdo.engine.DatabaseImpl.<init>(DatabaseImpl.
> > java:183)
> > at org.exolab.castor.jdo.JDO.getDatabase(JDO.java:623)
> > at de.devlogix.app.JDOTest.<init>(JDOTest.java:70)
> > at de.devlogix.app.JDOTest.main(JDOTest.java:129)
> >
> > As one can see, it happens at JDO.getDatabase(). Now where is
> > the problem? I searched google about it and found that Nadja
> > Senoucci had the same problem, but it seems that it was a
> > spelling error in his program.
>
> I found more about this. I tried to debug into castor code
> and got to the point where the exception is thrown the first
> time. In the class DatabaseRegistry, in the method
> getDatabaseRegistry( String name ) there is the following expression:
>
> dbs = (DatabaseRegistry) _databases.get( name);
>
> Now I inspected the hashtable _databases a bit more. There is
> only one entry in it. But the key for this entry is "test"
> instead of "testdb". The value however is referring to the
> correct entry. So where can this problem be found? Is it a
> configuration error on my side (I didn't find any), or is it
> a problem that my database name ends with "db"? Or is it
> something else?
OK, I found it. It was a configuration error. I have set the name for the db
in the database.xml to test.
Bye
Marco
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
