On 3/26/2007 10:33 AM, [EMAIL PROTECTED] wrote:
Hi Reinhard,
No offence, but this looks really ugly ... what is the intention of generating
output that requires that type of hack?
The thing you find ugly, apparently, has to do with how XSLT operates on
namespaces. So blame the W3C XSLT spec team.
The validation transformer isn't to blame. Of course it could avoid
using a namespace at all, but that would present different problems.
Lars
Regards,
Chris
-----Ursprüngliche Nachricht-----
Von: Reinhard Poetz [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 26. März 2007 17:31
An: [email protected]
Betreff: Re: Transform the output of the ValidationReportTransformers in XSL
[EMAIL PROTECTED] wrote:
[snip]
Could someone tell me why this is that way
I think that the match rules apply to empty namespaces and not the default
namespace.
and how I can convince the validation-report transformer to stop adding the
namespace stuff to the output?
Well at the moment I got everything to work, by modifying the Transformers
code, but that can't really be the optimal solution.
this might help, though haven't tested it:
<xsl:stylesheet xmlns:v="http://apache.org/cocoon/validation/1.0";
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="2.0">
<xsl:template match="/v:report">
<test>
<xsl:copy-of select="v:error"/>
</test>
</xsl:template>
</xsl:stylesheet>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
