Sylvie,
it actually does .. ;-(. Have a look at the corresponding jdo-conf.xsd, and
you'll see that it does by definition. Looks like it has been overlooked to
make this change in jdo-conf.dtd when changing jdo-conf.xsd.
Iow,
<jdo>
<database>
...
</database>
<database>
...
</database>
<transaction demarcation mode=local"/>
</jdo>
should do the trick in your case. Once you have tried this (successfully), can
you please file a bug report about the incorrect jdo-conf.dtd?
I hope this helps.
Werner
-----Urspr�ngliche Nachricht-----
Von: SYLVIE PALLUEL [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 03. M�rz 2005 10:09
An: [email protected]
Betreff: Re: [castor-dev] Pb with loadConfiguration while using
simultaneously two databases
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
> ��: [email protected]
> 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: [email protected]
> 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
