Charles Anthony wrote:
Hi Thomas,
There is another mitigation to this problem: you can switch on loading a serialized version of the repository in OJB.properties. This will eliminate the parsing of repository.xml. (Well on the first start it still get's parsed...)
Hmm... looking at the CVS version of RepositoryPersistor, it seems that the only time a serialized version is created is as a temp file, which is deleted on exit. The serFile attribute is checked to see if it is not null; the only place it is given a value is as a delete-on-exit temp file.
So, I'm not sure that that the feature is working as intended. My "guess" was that just turning on the property would create a serialized file, which would be loaded next time round. That doesn't seem to be the case.
I checked the code and found that you are right. The important change was made by Armin two month ago: http://cvs.apache.org/viewcvs/db-ojb/src/java/org/apache/ojb/broker/metadata/RepositoryPersistor.java.diff?r1=1.10&r2=1.11&diff_format=h
He states that it was to fix a problem, but I don't remember the actual problem.
I could imagine that it is related to the separation of classdescriptors and connectiondescriptors. May Armin remembers.
IMO it would be good to maintain the old sematics of RepositoryPersistor which allowed to keep a serialized version of the repository accross several relaunches of an application.
thoughts?
cheers, Thomas
Cheers,
Charles.
This email and any attachments are strictly confidential and are intended solely for the addressee. If you are not the intended recipient you must not disclose, forward, copy or take any action in reliance on this message or its attachments. If you have received this email in error please notify the sender as soon as possible and delete it from your computer systems. Any views or opinions presented are solely those of the author and do not necessarily reflect those of HPD Software Limited or its affiliates.
At present the integrity of email across the internet cannot be guaranteed
and messages sent via this medium are potentially at risk. All liability
is excluded to the extent permitted by law for any claims arising as a re-
sult of the use of this medium to transmit information by or to HPD Software Limited or its affiliates.
--------------------------------------------------------------------- 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]
