Hi Stefan, I suppose you are using 0.9.8 version of OJB. The "default" repository file has to know about all class-descriptors of the system. Use a entity references to make the default repository known of all class-descriptors. For example see the repository_farAway handling. HTH
In the next version, the multiple database handling will be easier to use. One repository, multiple jdbc-connection-descriptors. So stay tuned ;-) regards, Armin ----- Original Message ----- From: "Stefan Schl�sser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 22, 2003 11:09 AM Subject: Possible bug in QueryFactroy when using multiple repositories ? Hi, I am using 2 separate pbkeys with 2 separate repositories to map onto 2 different databases as described in an earlier mail. This works fine with the brokers, at run-time, their descriptor repository holds the different definitions (debugger). When trying to create a new Query using Query query = QueryFactory.newQuery(cls , crit); A .ClassNotPersistenceCapableException is thrown, looking into the sources reveals access to a default repository. This only contains elements of the first brokers' repository. Even though there might be a way to set this repository before using the query factory, this does not seem a thread-safe way of doing it. Am I misusing the API ? How can I tell the query factory which repository to use ? Can I create a query using the broker (which contains the correct repository) ?? Thanks for any help, Stefan Schl�sser -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
