Re: Field Descriptor's ID clash in multi database environment

[Thomas Mahler]

You simply have to use different toplevel repositories to connect to different RDBMS.

Stephen Ting wrote:

Hi Thomas,

You means I can't have same class.descriptor included in the repository.

What I actually did is as follow;

<!-- defining entities for include-files -->
<!DOCTYPE descriptor-repository SYSTEM "repository.dtd" [
<!ENTITY user SYSTEM "repository_user.xml">
<!ENTITY internal SYSTEM "repository_internal.xml">
<!ENTITY sytbtu SYSTEM "repository_userB.xml">
<!ENTITY sytmyy SYSTEM "repository_userC.xml">
]>

Whereas in the repository_user.xml, repository_userB.xml and
repository_userC.xml
The class.descriptor declared are exactly the same. I am doing this
because all the databases
have the same schema.
I can't think of a way to avoid the conflicts, do you have a better way
to do this?
Thanks in advance

Regards,
stephen

-----Original Message-----
From: Thomas Mahler [mailto:thma@;apache.org] Sent: 01 November 2002 16:47
To: OJB Users List
Subject: Re: Field Descriptor's ID clash in multi database environment


Hi STephen,

Stephen Ting wrote:

I am using the PB api in multiple databases environement. When i persist
javabean(BO) the following error occured. Could anyone give me some
insight on what's happening?

[Error] repository_userB.xml:14:25: Attribute value "my.com.shinyang.einout.business.bo.InventoryBO" of type ID must be unique within the document. [Error] repository_userC.xml:14:25: Attribute value "my.com.shinyang.einout.business.bo.InventoryBO" of type ID must be unique within the document.

Actually, in another repository file, that's repository_user.xml. I have the same BO declared. Is it the ID field clash. How to resolve the problems.

The repository.dtd uses class names as unique IDs to identify class-descriptor elements.
It is not allowed to have two class.decriptors for the same class in one repository.
The error message you get is quite precise in this respect.

You must organize your xml include files in a way to avoid such conflicts.

cheers,
Thomas

thanks in advance.

regards,
Stephen

--
To unsubscribe, e-mail: <mailto:ojb-user-> [EMAIL PROTECTED]>
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>

--
To unsubscribe, e-mail:   <mailto:ojb-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>