Hi David,

----- Original Message -----
From: "David Mitchell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 21, 2003 12:23 AM
Subject: repository questions


>
>  I have two questions about the repository definitions:
>
>  1- is it possible to tell OJB not to check for the existence of the
> persistent classes defined in the repository file?

Sorry, I have made OJB more strict when reading the repository file
to avoid runtime errors caused by missed classes.
But in CVS is a new version of the MetadataManager is checked in,
which allows to add repository files (.xml files with class descriptors)
at runtime.
So start OJB with basic tables and load other class-descriptors
if needed. Use:
readDescriptorRepository(String fileName)
mergeDescriptorRepository(DescriptorRepository repository)

> My application has
> several hundred tables, and the full repository file takes quite a
while to
> load on my slow machine every time at application startup. For the
moment
> that only thing I can think of is to remove all table defintions from
the
> file that im not actually using in my code (3/4 of the tables)
>
>  2- could collection-descriptors for a set of persistent objects be
merged
> from a second file? My problem is the repository_XXX file is
auto-generated,
> and I havent figured out a good way to make the template insert the
> collection definitions in the referenced objects automatically.
> Alternatively, it would be great if I could put those defintions in a
> separate file from the generated one, then merge the manually-created
values
> after loading the generated values.

Currently there is no attempt in that direction,
but you could implement this by your own:
Read your collection definitions and use the
MetadataManager/DescriptorRepository to
update your class-descriptors.

regards,
Armin
>
>  thanks for any feedback,
>  -dave
>
>
>
> +---------------------------------------------------------+
> This message may contain confidential and/or privileged information.
If you
> are not the addressee or authorized to receive this for the addressee,
you
> must not use, copy, disclose or take any action based on this message
or any
> information herein.  If you have received this message in error,
please
> advise the sender immediately by reply e-mail and delete this message.
> Thank you for your cooperation.
> +---------------------------------------------------------+
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to