Hi Gerrit,
Response inline...
> Hi Helder, thanks a lot for your tips.
Glad to know it helped! :-)
> I used your line taken from [1], and it worked. Apparently, you have to
> pass a qualified attribute name which includes the prefix. This is even
> specified in the org.w3c.dom.Element interface.
Humm... AFAIK, the prefix is not required to handle things internally.
A document serialization, though, will need to add the proper
prefixes. I recall doing things like
setAttributeNS("http://www.w3.org/1999/xlink";, "href", "somelink") in
Firefox, just as proof-of-concept. Although the DOM will not look as
intuitive as when including the prefix, everything should work as
expected. :-)
> I also browsed the SVN repository, and it seems that XLinkSupport is
> still omitting the prefix.
[...]
> Same goes for all other attribute getters and setters in XLinkSupport.
> Should I maybe file a bug somewhere or are these functions intended to
> work in another way?
I guess you have bumped at bug 45520 [1], which was actually a bug in
the serializer. It was fixed after the 1.7 release so I'd suggest
confirming that the current trunk code [2] does no longer reproduce
the problem you were experiencing. Please report back if you are able
to! ;-)
> Regards,
> Gerrit
Cheers,
Helder
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=45520
[2] http://xmlgraphics.apache.org/batik/download.cgi#Subversion+repository
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
