Hold OJB internal tables in another RDBMS

[Peter Gaus <pe...@gaus-net.de>]

Hi,

I'm using the ODMG API and I have the following issue:

ODMG uses the OJB internal tables, which according to the specification
(see OJB basic concepts) must be in the target RDBMS. My question is
now: Is there a way to hold the OJB internal tables in a
different/independent RDBMS for themselve and then connect to an extra
RDBMS where only my application specific tables resist.

Here's an extract of my repository_database.xml I use:

********* repository_database.xml - begin *************
<jdbc-connection-descriptor
      jcd-alias="ojb"
      default-connection="true"
      platform="MySQL"
      jdbc-level="2.0"
      driver="org.gjt.mm.mysql.Driver"
      protocol="jdbc"
      subprotocol="mysql"
      dbalias="//localhost:3306/ojb"
      username=""
      password=""
/>  <jdbc-connection-descriptor
      jcd-alias="myAppl"
	default-connection="false"
      platform="MySQL"
      jdbc-level="2.0"
      driver="org.gjt.mm.mysql.Driver"
      protocol="jdbc"
      subprotocol="mysql"
      dbalias="//localhost:3306/myAppl"
      username=""
      password=""
/>
********* repository_database.xml - end ***************

I want that the OJB internal tables resist in the default connection
"ojb". My user specific tables should be in the database "myAppl".

Could someone help me, please.

Thanks,
Peter