Hello, On 19.03.2004 11:24:07 Wlid Yemah wrote: > > I have the following database configuration file > containing one jdo mapping file 'demo-jdo1.xml': .. > My program starts and loads succesfully this file and > everything goes as expected. During runtime (i.e., > without having to stop my program and restart it > again), I want to include another mapping file, so I > make my program load the configuration file which now > looks like: .. > The file is loaded succesfully (at least it looks like > it) however when I query on a class that is mapped in > 'demo-jdo2.xml' I get an exception: > > org.telecare.core.exception.JdoCastorException: > org.exolab.castor.jdo.ClassNotPersistenceCapableException: > The class demo.Address is not persistence capable: no > mapping was defined for the class > > Class 'demo.Address' is well mapped in 'demo-jdo2.xml' > but it seems that this mapping file has not been > really loaded, and only the mappings defined in > 'demo-jdo1.xml' (which is probably cached in memory) > is (re)used during my query. So how to force Castor to > reload a database configuration file which has changed > (in my case by adding another mapping file)? Any help > would be greatly appreciated.
I had a similar problem when trying to change to database connection at runtime and posted an enhancement request to Castor's Bugzilla. It also contains the patch I am currently using to get what I need: http://bugzilla.exolab.org/show_bug.cgi?id=1511 Regards, Martin ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
