Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Why does Doctype change processing of a document

Why does Doctype change processing of a document

2007-05-02       - By Ferdinand Soethe
Reply:     1     2     3     4     5     6     7  



-------- Original Message --------
Subject: Re: Why does Doctype change processing of a document
Date: Wed, 02 May 2007 20:03:38 +0200
From: Ferdinand Soethe <ferdinand@(protected)>
To: Larry Trammell <larryt@(protected)>
References:
<22A20AD271DB4949836F85AACBB90A770892A0@(protected)>

Thanks to all of you for helping me understand my mistake. At least I
know what is going wrong now.

Adding xmlns:xhtml="http://www.w3.org/1999/xhtml" to my stylesheet
worked well but added all those ugly xhtml:... to the generated elements.

So I declared xhtml as default namespace
xmlns="http://www.w3.org/1999/xhtml" to make them disappear.

Which worked really well in this template and let to the resulting
document being free of xhtml:...

> <xsl:stylesheet
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns="http://www.w3.org
/1999/xhtml"
>     version="1.0" >
>    
>     <!-- toolbox for copying everything over to the target -->
>     <xsl:import href="copyover.xsl"/>
>    
>     <!-- Match html, disregard the namespace -->
>     <xsl:template match="/*[local-name()='html']">
>         <xsl:apply-templates select="*[local-name()='body']"/>
>     </xsl:template>
>    
>     <!-- Match body, disregard namespace -->
>     <xsl:template match="/*[local-name()='html']/*[local-name()='body']">
>         <div class="content">
>             <xsl:apply-templates/>
>         </div>
>     </xsl:template>

except for the div-element.
Has anyone the patience to explain?

And also: I expected to be able to do away with /*[local-name()='html']
now that xhtml is default namespace. But it doesn't work that way. Why?

And when I change the style-sheet to

> <xsl:stylesheet
>     xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="http://www
.w3.org/1999/xhtml"
>     version="1.0" exclude-result-prefixes="xhtml">
>    
>     <!-- toolbox for copying everything over to the target -->
>     <xsl:import href="copyover.xsl"/>
>    
>     <!-- Match html, disregard the namespace -->
>     <xsl:template match="/*[local-name()='html']">
>         <xsl:apply-templates select="*[local-name()='body']"/>
>     </xsl:template>
>    
>     <!-- Match body, disregard namespace -->
>     <xsl:template match="/*[local-name()='html']/*[local-name()='body']">
>         <div class="content">
>             <xsl:apply-templates/>
>         </div>
>     </xsl:template>
>    

and try to remove xhtml with  exclude-result-prefixes then things turn
around. div will no longer have a namespace attribute while all the
copied element do. Misterious really.

Best regards,
Ferdinand Soethe