>>> in addition to oor:finalized you can use oor:mandatory here so the >>> content can't be changed and removed. >> That did the trick! Thanks a lot, that's exactly what I need! > > I was too fast ... :( > > In fact this works great when adding to a node in the shared > configuration layer > (share/registry/org/openoffice/Office/DataAccess.xcu, in my case). Doing > the very same for a node in the user config layer, or the > user/uno_packages config layer (the latter is what I would need it for), > does not work at all - I can easily delete the node, without any > complaint from the configuration service :(
Stupid me. I added the attribute to a .xcu file in an already installed extension, and was obviously fooled by some cache. Adding the attribute before the extension is installed works like a charm. So, what's left is that the attribute doesn't wok in the user layer - which probably makes sense, the user layer comes into existence only by the user writing data, and is the top level layer. Supporting "mandatory" nodes here might be overkill, and completely unneeded. So, oor:mandatory is what I need ... Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
