I thought I would mention that the unstable builds should now have a fix for this issue. Instead of filering namespaces at the XSLT level, they are filtered in specific processors, like the XML:DB processor (so that the infoset produced by Saxon, for example, does not get corrupted by such filtering, and can be used as is for example by another downstream XSLT transformation).

-Erik

Matthew J. Graham wrote:
Hi,

A workaround I have found is to add the following code to org.orbeon.oxf.processor.transformer.xslt.XSLTTransformer.java at line 135:

public void startPrefixMapping(String s, String s1) thro
ws SAXException {
if ("xmlns".equals(s)) {
return;
}
// Start of my added code
if (s.length() > 0 && s1.equals("")) {
return;
}
// End of my added code
super.startPrefixMapping(s, s1);
}
}));


So this gets rid of the xmlns:xs="" type statements. Unfortunately there seems to be another problem concerning attributes with namespace, e.g. xsi:type with replication of the namespace so in the document that it being submitted to eXist, they appear as xsi:xsi:type, which throws an exception.

    Cheers,

Matthew


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user

Reply via email to