AttributeList.set(int,Attribute) may have false positive Namespace Collision issue #90

rolfl opened this Issue Aug 27, 2012 · 0 comments


None yet

1 participant

rolfl commented Aug 27, 2012

Namespace collision happens when the new Attribute will require two different namespace URLs wit the same prefix to be in scope for an Element. Setting an attribute position to a new attribute may cause a namespace collision if the new attribute has the same prefix, but different URL, as an existing item in the Element.

But, if the only collision is with the attribute that is being replaced, then there is no collision.... but the current checkNamespaceCollision does not take the replaceing-the-collision-attribute in to consideration, and it should.

@rolfl rolfl added a commit that closed this issue Sep 2, 2012
@rolfl rolfl Fixes #90 - false-positive error validating namespace collisions when…
… 'setting' an Attribute.
@rolfl rolfl closed this in 500f9e5 Sep 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment