Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 362006

Summary:

[api] Element.getAttributeNode will create an Attribute for implied values

Product:

[WebTools] WTP Source Editing

Reporter:

Nick Sandonato <nsand.dev>

Component:

wst.xml

Assignee:

Nick Sandonato <nsand.dev>

Status:

RESOLVED FIXED

QA Contact:

Nitin Dahyabhai <thatnitind>

Severity:

normal

Priority:

CC:

walter.brunauer

Version:

3.4

Keywords:

api, plan

Target Milestone:

3.4 M3

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
patch	none

Description Nick Sandonato

2011-10-25 16:50:29 EDT

In the process of making sure implied values are returned for getAttribute, it looks like the functionality was carried over to getAttributeNode. The spec, however, reads that if the node by that name doesn't exist, null should be returned.

This will change getAttributeNode back to returning null even if a default value is suggested. getAttribute will continue to suggest the default value if the named attribute does not exist. To play it safe, and not break anyone in Indigo relying on this misbehavior, I'm targeting for Juno.

Comment 1 Nick Sandonato

2011-10-25 16:52:44 EDT

Created attachment 205951 [details]
patch

Comment 2 Nick Sandonato

2011-10-25 16:56:27 EDT

Code checked in.