DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29411>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29411 XSLTC generates uneccessary preifix/URI mappings to serializer ------- Additional Comments From [EMAIL PROTECTED] 2004-06-10 22:48 ------- Hi Santiago, could you attach the patch to this bug so I can have a look? Thanks. I've started to have my doubts about this one after doing the work for bug 29488 for Xalan-J interpretive. I've been working on a similar patch for XSLTC. While working on that fix for Xalan-J interpretive I saw the same sort of behavior, multiple redundant calls. But I did find a situation where those "redudant" calls weren't so redundant. <elem1 xmlns:pfx1="uri1"> <elem2> <xsl:attribute pfx1:attr xmlns:pfx1="replaced">value1</xsl:attribute> <pfx1:elem3 /> </elem2> </elem1> which was serialized to: <elem1 xmlns:pfx1="uri1"> <elem2 pfx1:attr="value1" xmlns:pfx1="replaced"> <pfx1:elem3 xmlns:pfx1="uri1"> </elem2> </elem3> ... and it was those extra calls, re-declaring the prefix mappings on elem3 that got pfx1 set correctly back to "uri1" that was good to have. - Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
