I didn't develop something like this for the backup tool. What I did was adding a flag in the PropInfo class for this purpose.
As Stefan wrote: "no. great care has been taken so far to avoid loopholes in the core in order to prevent security/data consistency issues." It seems your issue is a lot more common than expected: sometimes, we need to escape protected checks. Maybe we should add the flag you describe but allow it only for custom node types. If you can create consensus on this, I would be happy to help you on this. Actually, it would ease the backup tool's life a lot. What do you think? Nico my blog! http://www.deviant-abstraction.net !! On 9/19/06, David Kennedy <[EMAIL PROTECTED]> wrote:
What I'm really looking for is something as simple as a flag/bit on the setProperty methods (e.g. setProperty(propertyName, Value, overrideProtected)). Importing an XML stream may be a little too heavyweight for my usage. David
