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.

Bug 17699 - TreeDocument's setDocumentType and setDocumentElement should not allow replace old set node
Summary: TreeDocument's setDocumentType and setDocumentElement should not allow replac...
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: TAX/Lib (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@xml
URL:
Keywords: API
: 17928 (view as bug list)
Depends on:
Blocks: 26478 20532
  Show dependency tree
 
Reported: 2001-11-15 11:33 UTC by _ lkramolis
Modified: 2007-09-25 06:06 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ lkramolis 2001-11-15 11:33:29 UTC
TreeElement.setAttribute method should throw some Exception when element already
contains attribute with same name as parameter.

Another solution could be that setAttribute method will still remove attribute
with same name and always add specified attribute. New method addAttribute could
throw exception, when exists attribute with same name.

Do not know, which solution is better, may be that 2 methods is better than 4
methods.
Comment 1 _ lkramolis 2001-11-21 16:12:17 UTC
*** Issue 17928 has been marked as a duplicate of this issue. ***
Comment 2 Jan Chalupa 2001-11-27 17:39:08 UTC
Target milestone -> 3.3.1.
Comment 3 Jan Chalupa 2001-11-27 17:42:40 UTC
Target milestone -> 3.3.1.
Comment 4 _ lkramolis 2001-12-04 17:07:32 UTC
TreeElement has class addAttribute which throw exception, when
attribute with same name exists.

Similar problem is in TreeDocument class and its setDocumentElement
and setDocumentType methods. Those methods should throw exception,
when there is already such node.
Comment 5 _ lkramolis 2002-01-10 08:31:22 UTC
I rolled back throwing exception from TreeElement.addAttribute (this
will fix #19221). This will be again implemented after 3.3.1 release.
Comment 6 _ pkuzel 2002-06-03 12:28:14 UTC
Let these are considered while planning next release.
Comment 7 Marek Grummich 2002-07-19 16:15:54 UTC
Target milestone was changed from not determined to TBD
Comment 8 _ pkuzel 2002-08-13 18:15:48 UTC
It is subtask of issue 26478.