Hi Russel, Russell Smyth wrote:
In the doc for the repository.xml there is the following statement:The documentation is not accurate in this respect. In the early days of OJB you could specify a jdbc-connection per class.
"The jdbc-connection-descriptor element specifies the default jdbc connection for the repository. All class-descriptor elements that do not specify their own jdbc-connection-descriptor will use the default jdbc connection"
This statement implies that class-descriptor elements
can specify a jdbc-connection-descriptor, however the
dtd does not reflect this, nor does it work (I tried!)
AT some point in time we decided to have only one jdbc-connection-descriptor per repository.
If you want to work with multiple DBs in parallel you can still do it. You just have to work with multiple broker working against multiple repositories.
SO the idea is to have class A defined in Repository RepA and Class B in RepB.
RepA points to databaseA and RepB to databaseB.
The only drawback of the new solution: Your application must know that A must be looked up in RepA and not in RepB. You will need some additional configuration mechanism to hold this information.
cheers,
Thomas
Is there a way to do per-class jdbc-connection config? I honestly am not sure how this would work, but it would be very usefull for my current application where we have one set of data in one db and another in another, and they are logically related, so we would like to have ojb perform the relation for us.Thanks Russell -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
-- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
