hi jacco
let me take a closer look at this next week.
... at a first glance, i assume that there is a bug in NodeImpl: the corresponding call creating a new child node does in fact use a diffent way to access the item. that's probably wrong with createChildProperty. i'll verify it (still next week ;) and keep you informed. regards angela
