hal at idi.ntnu.no
Wed Jan 30 13:33:47 PST 2002
> elt.getAttribute("foo").setValue("bar") will not drop the existing
> elt.setAttribute(new Attribute("foo", "bar")) of course will do a
> elt.setAttribute("foo", "bar") is a convenience method for the above
> syntax, which is why it does a replacement. One could argue it
> shouldn't, and one can argue it should.
I would've thought the latter was equivalent to
Attribute attr = elt.getAttribute("foo");
if (attr != null)
elt.setAttribute(new Attribute("foo", "bar"));
What is the motivation for the "always replace" logic? I don't get it. If
the reasons are good, perhaps we need an ensureAttribute method?
More information about the jdom-interest