This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
|Summary:||Regression: XMLDO ignores custom node|
|Product:||platform||Reporter:||Jan Pokorsky <jpokorsky>|
|Component:||Data Systems||Assignee:||phamernik <phamernik>|
|Issue Type:||DEFECT||Exception Reporter:|
|Bug Depends on:||20532|
Description Jan Pokorsky 2002-02-22 14:51:10 UTC
The custom node offered by Environment.Provider is ignored. XMLDO shows just some own node (XMLDataNode??). If the xml module is disabled everything works well.
Comment 1 _ pkuzel 2002-02-22 15:20:07 UTC
Sorry Jan, but it is intentional behaviour. Simply imagine that XML module provides Environment.Provider returning its own XMLDataNode.
Comment 2 _ pkuzel 2002-02-22 15:52:36 UTC
- XMLDataObject's protected createNodeDelegate() modifies DataObject's protected createNodeDelegate() semantics. - DataObject's public final getNodeDelegate() semantics is described using protected createNodeDelegate(). - XMLModule's XMLDataObject subclass modifies createNodeDelegate() semantics. It is allowed. I consider it as API bug. Of course we can workaround it in XML module, but only as last resort.
Comment 3 Jesse Glick 2002-03-01 16:51:46 UTC
I think #19491 captures the basic discussion, and has a workaround. We should either (1) implement issue #20532 and deprecate providing a Node at all (it never worked with the XML module installed), or (2) try to fix the problem in the XML module, i.e. support the API even though it is not "nice". (1) would be preferable IMHO if we can do it for 3.4. *** This issue has been marked as a duplicate of 19491 ***
Comment 4 Quality Engineering 2003-07-01 15:57:06 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 5 Quality Engineering 2003-07-01 16:31:57 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.