[ http://issues.apache.org/jira/browse/OJB-68?page=comments#action_12319903 ]
Jakob Braeuchi commented on OJB-68: ----------------------------------- imo the following should work: prevent firing of the LifeCycleEvent in rsIterator#next() when the iterator is created by QueryReferenceBroker#getCollectionByQuery. the LifeCycleEvent s are fired after execution of the RetrievalTask, so the objects should be fully materialized. to disable the LifeCycleEvent in RsIterator we need additional methods in OJBIterator. > Query/reference prefetching issue: PersistenceBrokerAware#afterLookup(...) is > called before the object was completely materialized > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: OJB-68 > URL: http://issues.apache.org/jira/browse/OJB-68 > Project: OJB > Type: Bug > Components: JDO-API, ODMG-API, OTM-API, PB-API > Versions: 1.0.3 > Reporter: Armin Waibel > Assignee: Jakob Braeuchi > > PersistenceBrokerAware#afterLookup(...) is called before the object was > completely materialized. The "normal" fields are materialized, but all > references still 'null' when the afterLookupEvent is fired. The > query/reference prefetching in class QueryReferenceBroker is responsible > because it seems that this class batch the retrieve of references. > Test case to reproduce this issue is PBListenerTest#testStoreAndQuery(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
