This one time, at band camp, Cerny Christian said:
CC>I have 2 different Oracle DBs which i want to connect thru 2 different
CC>poolman Datasources with castor.
CC>For achiving this i have an poolman.xml file defining the two pools and
CC>there names.
CC>Futhermore I'm generating two jdo-conf files on the fly and pass it to JDO.
CC>The problem now is that castor always uses the same poolman pool.
CC>Castor does use the right jdo-conf for the database-name (tries to map on
CC>wrong tables cause of the wrong mapping files read ...),
CC>but it always uses the first pool in poolman.xml !
CC>If I do tests with poolman standalone, I'am able to lookup and use different
CC>pools in the poolman config.
CC>How does castor lookup the datasource ? Do I have any configuration issues ?
CC>Wrong params in the DataSource Config ?
CC>
CC>Any ideas ? thanks for your help !
Christian,
Castor simply uses the DataSource that is specified in the database
descriptor. As for looking up the correct dbname in the PoolMan
descriptor, that should be the job of PoolMan. I've used PoolMan
quite a bit, but not in this manner. I'll bet that there are accessor
and mutator methods on PoolMan's metadata for the dbname. However,
because Castor does not provide a facility for passing arguments
down to PoolMan describing which dbname to utilize, it seems like
PoolMan would simply make use of the first one in its descriptor.
I'm only guessing but I'll bet that the problem lies here.
As for a solution, if you're so inclined, dig into the code to see
if you can design a nonintrusive fix. However, I can tell you that
Castor can currently only make use of one database in the space of
a single transaction.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
