The most easy approach is to use instance callbacks. See http://db.apache.org/ojb/tutorial3.html#instance%20callbacks.
you can place the additional lookup logic into the afterLookup callback The storage logic can be placed in the afterInsert callback.
Only "disadvantage" of this approach: you persistent class must implement the OJB interface PersistenceBrokerAware.
cheers, Thomas
Claus Radloff wrote:
Hello,
I�d like to provide OJB with my own class to load/store objects in the database. This is because I can�t get OJB to load this kind of beans, as they consist of multiple rows in the same table.
To be able to load other classes with OJB, which reference these objects, I would like to tell OJB somehow to use my own implementation. Is there a possibility to do so?
What I imagine is something like: <class-descriptor class="my.SpecialBean" storage-class="my.SpecialBeanStorage"/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
