Hi, it's me again :-)
Believe it or not, I have even more questions.
I somehow think the method outlined in my previous posting is a bit overwhelming. I'd have to update three xml-files and provide separate lookup code for different versions.
Wouldn't it be easier to just provide two getters for the same relation, and just alter the client code slightly, ie. when I just want to display a list of children I'd just call getChildrenRO(), while I'd call getChildrenRW() when I want to add or delete children in the collection.
Still I'd have to provide a separate relation in ejb-jar.xml, but the amount of xml-configuration would still be significantly lower, which I think is a good thing.
I don't know if this would work, but I'd like to get a hint here, I guess I could dream up one crazy scheme for implementing this kind of optimization after the other, and it's just end up as a horrible mess.
Jon Martin Solaas