Re: Flattened relationship and iterator oddness
Re: Flattened relationship and iterator oddness
- Subject: Re: Flattened relationship and iterator oddness
- From: John Larson <email@hidden>
- Date: Fri, 8 Sep 2006 17:02:21 -0500
Fabian,
I discovered this a month or two ago. It appears as if iterator()
does not fire the fault on relationships. That is why with your log
statement everything is ok: the accessing of the productionRuns()
field IS firing the fault. The iterator then works. This is a bug
in the iterator implementation. The only thing you can do is either
manually fire each fault or use objectEnumerator(). I use
objectEnumerator().
John
On Sep 8, 2006, at 4:28 PM, Fabian Peters wrote:
Hi,
I've got the following entities:
Order <->> OrderItem <<->> ProductionRun <-> DeliveryDefect
In Order, I've defined a flattened relationship deliveryDefects. It
works fine for deliveryDefects that exist when the order is fetched
from the DB. However, it fails to include a deliveryDefect that is
created and then saved to the DB. Is this a known limitation of
flattened relationships?
Not all too important since I can of course get to it myself. Part
of my first implementation looked like this:
for (Iterator iter = orderItems().iterator(); iter.hasNext
();) {
OrderItem anOrderItem = (OrderItem) iter.next();
// log.debug("production run count: " +
anOrderItem.productionRuns().count());
for (Iterator iterator = anOrderItem.productionRuns
().iterator(); iterator
.hasNext();) {
ProductionRun aProductionRun = (ProductionRun)
iterator.next();
if (aProductionRun.deliveryDefect() != null)
deliveryDefects.addObject
(aProductionRun.deliveryDefect());
}
}
Now, I'm using WO 5.3 with java 1.5.0, so I assumed this should
work. But it fails due to iterator.hasNext() always returning
false. While debugging, I introduced the log statement that is
commented out above. With that in place, the iterator starts to
behave correctly!?
I'd really like to understand what's going on here! Is the
productionRuns() fault not getting fired by the iterator? Is this
intended/documented?
Now I'm back to using good old Enumeration which works w/o further
ado.
Any comments most welcome...
Fabian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden