Hi Rick,
Rick G wrote:
Is there a preferred way to initialized OJB when starting a web app?
Currently, on my system, OJB doesn't really load up until the first DB
related call. Was wondering if there were some call I could make to an OJB
Factory class or whatever, to initialize OJB, other than making a call that
would invoke a query.
OJB doesn't have a specific startup procedure, but you can lookup and
close a PersistenceBroker instance to initialize OJB (think this will
load metadata classes).
On a side note, is there a way to pragmatically get the configured OJB Cache
setting? Other than reading it out of the repository_database.xml file of
course.
To get the cache class defined in the jdbc-connection-descriptor you can
use the metadata classes, e.g. lookup a PB instance and do
Class cacheClass =
broker.serviceConnectionManager().getConnectionDescriptor()
.getObjectCacheDescriptor().getObjectCache()
regards,
Armin
Thanks for any tips/suggestions,
Rick Gavin
---------------------------------------------------------------------
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]
