Sylvie,
we are aware of problems with multiple database configurations at JDO2 as this has been reported at bugs 1742 and 1865. Also bugs 1781 and 1865 relate to different issues of creating JDO2 instances.
I have started to work on this some days ago but don't have a patch available yet as I need to discuss some concepts with Werner and Martin first.
For your specific problem can you please send me a short test case. I'll have a look at it this evening and try to create a patch for your specific problem.
Regards Ralf
SYLVIE PALLUEL schrieb:
Werner,
The file jdo-conf.dtd contains this:
<!ELEMENT jdo-conf ( database,transaction-demarcation ) >
and doesn't support many database element.
So, How can I do?
Sylvie. ___________________ CREDI RA Sylvie Palluel
[EMAIL PROTECTED] ___________________
-----Message d'origine----- De : Guttmann Werner MAX SD [mailto:[EMAIL PROTECTED] Envoyé : jeudi 3 mars 2005 09:33 À : castor-dev@exolab.org Objet : Re: [castor-dev] Pb with loadConfiguration while using simultaneously two databases
Sylvie,
I actually don't know whether we really support two separate JDO configuration files or not, but can you please try to move the two <database> definitions into one configuration file, if this is an option to you. Apart from this, there's a bug report out there that does not match your problem 100%, but the resolution of which might address your problem partially.
Regards Werner
-----Ursprüngliche Nachricht----- Von: SYLVIE PALLUEL [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 03. März 2005 07:50 An: castor-dev@exolab.org Betreff: [castor-dev] Pb with loadConfiguration while using simultaneously two databases
Hi,
I've just integrated Castor 0.9.6 in my application.
I'm using two distinct database accesses (2 databaseFileConfig, 2 database names).
But when I try to initialize the JDO objects like this:
JDO2.loadConfiguration(databaseFileConfig1,loader); JDO2 jdo1 = JDO2.createInstance(nomDatabase1);
JDO2.loadConfiguration(databaseFileConfig2,loader); JDO2 jdo2 = JDO2.createInstance(nomDatabase2);
I've have an exception on the second loadConfiguration. In fact, after looking for the problem, I have to call JDOConfLoader.deleteConfiguration(); To reset private static boolean _loaded to false, before calling the new JDO2.loadConfiguration(..).
But is this ok, or may I have other pb later in my transactions ?
I have the same pb using the old JDO object (getDatabase() is calling loadConfiguration(..)) :
JDO jdo1 = new JDO(); Jdo1.setClassLoader(loader); Jdo1.setDatabaseName(nomDatabase1); Jdo1.setConfiguration(databaseFileConfig1);
Database db1 = jdo1.getDatabase();
JDO jdo2 = new JDO(); Jdo2.setClassLoader(loader); Jdo2.setDatabaseName(nomDatabase2); Jdo2.setConfiguration(databaseFileConfig2);
Database db2 = jdo2.getDatabase();
Thanks for your help.
Sylvie ___________________ CREDI RA Sylvie Palluel
[EMAIL PROTECTED] ___________________
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
------------------------------------------------------------------------
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
--
Syscon Ingenieurbüro für Meß- und Datentechnik GmbH Ralf Joachim Raiffeisenstraße 11 D-72127 Kusterdingen Germany
Tel. +49 7071 3690 52 Mobil: +49 173 9630135 Fax +49 7071 3690 98
Email: [EMAIL PROTECTED] Web: www.syscon-world.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev