Related to this is also bug 214439:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=214439
This will add a test suite plugin for the W3C DOM Level 1 that can be
used to help test compliance.
Nick, I would highly suggest running this test suite once I get it
into CVS later this week during your testing for compliance. I have
plans to add DOM Level 2 and DOM Level 3 suites as well, but we need
to get DOM Level 1 compliance first.
Dave
NICHOLAS SANDONATO wrote:
In an effort to become more compliant with the W3C DOM specification,
we are planning to make changes that may require action on your
behalf. The current behavior of the WTP implementation of
org.w3c.dom.Element returns null for getAttribute(String) and
getAttributeNS(String) if the attribute value is not specified. After
the change, calls to these methods will return an empty string if the
attribute value is not specified. This change is required to comply
with the interface, and will correct various NullPointerExceptions
when EMF is used with our DOM implementation and the EMF code is
undeniably correct.
What is required?
If your code was depending on the DOM returning null to indicate a
missing attribute, the code should be changed to hasAttribute(String)
or hasAttributeNS(String) before obtaining the value.
When will this change be implemented?
During Milestone 3 of WTP 3.2.
Where can I find more information?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=272378
Thanks,
Nick
------------------------------------------------------------------------
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev