DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14403>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14403 Problem with remapping a prefix to a different namespace uri in a xml fragment. Summary: Problem with remapping a prefix to a different namespace uri in a xml fragment. Product: XalanJ2 Version: 2.0.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Xalan AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have an xml fragment x1, which has prefix "p1" mapped to URI "u1". I have another xml fragment x2, which has the same prefix "p1" mapped to a different URI "u2". I have a very simple XSL that merges the two by appending x2 after x1 and adding an outermost element. During this transformation, Xalan for some reason retains mapping in only one of the fragments (p1 specifically in x1). Now both u1 and u2 are also defined as targetNamespaces in their respective fragments. So this behaviour by Xalan would not have caused a problem under regular circumstances. But within x2 i have a "ref" attribute that is used to reference an element ( which is also within x2 ). But since ref always needs a namespace prefix it uses p1. But since only one of the prefixes have been retained, p1 now points to u1 and doesn't apply to x2 at all, resulting in Xalan complaining abt not being able to find the referenced element. An exhaustive search through the bug list didn't yield anything. Similary a search through various FAQs hasn't resulted in a convincing answer.
