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=27867>. 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=27867 DTM does not parse attribute namespaces properly ------- Additional Comments From [EMAIL PROTECTED] 2004-03-23 20:06 ------- I *think* this is a duplicate, though I haven't yet dug out the other copy. I don't think the problem is "parsing" per se. Instead, it's due to the fact that SAX can represent namespace declarations in several different ways (as attributes, as start/endPrefixMapping events, or both). Our SAX-driven DTM builder is currently configured to accept namespace declarations only as attributes. If you configure your SAX source to produce the declarations this way, everything works correctly. Take a look at how we configure Xerces when we're handed a streamsource, for example. It might be nice if we did that conversion automagically. I believe there is already an open request suggesting that we add this feature. There wasn't a great deal of demand for it, and there were some performance concerns, so it has never come to the top of our priority queue; it may, in fact, be listed as an Enhancement since this restriction was documented at one point. If someone wants to sketch out a proposed patch, feel free. Meanwhile, a workaround would be to plug in a SAX filter between your source and Xalan which buffers the startPrefixMapping events and converts them into attributes before the startElement is passed to us. Watch out for duplicates.
