I'd like CoreDocumentImpl.callUserDataHandlers() methods to be
protected instead of package private. The reason I'd like is that I
have a custom DOM implementation that extends DocumentImpl. I need
to override cloneNode(boolean) to make sure an instance of my own
Document implementation gets created instead of the parent
implementation. But then I can't access the callUserDataHandlers()
methods such as is being done in CoreDocumentImpl....
public Node cloneNode(boolean deep) {
CoreDocumentImpl newdoc = new CoreDocumentImpl();
callUserDataHandlers(this, newdoc, UserDataHandler.NODE_CLONED);
cloneNode(newdoc, deep);
return newdoc;
}
...or in DocumentImpl....
public Node cloneNode(boolean deep) {
DocumentImpl newdoc = new DocumentImpl();
callUserDataHandlers(this, newdoc, UserDataHandler.NODE_CLONED);
cloneNode(newdoc, deep);
// experimental
newdoc.mutationEvents = mutationEvents;
return newdoc;
}
If this is not objectionable, could this be done before the next release?
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
