> > > That's not the way to implement it. Your override of nodeLocalChanged and > nodeRemoteChanged should call super.nodeLocalChanged and > super.nodeRemoteChanged to signal your parent. The parent should > call its super if it places an override, so in the end MMObjectBuilders > nodeLocalChanged and nodeRemoteChanged is called. If you don't > call super then the Node cache of MMBase handled by MMObjectBuilder > nodeLocalChanged and nodeRemoteChanged will not operate as > intended. > My idea is not to override the changeLocalNode and changeRemoteNode methods in MMObjectBuilder. I just want to put an extra statement in those methods that will invoke the changeLocalNode/changeRemoteNode of the partentBuilder (if available).
greetings Rob
