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.
Aplogies [Re: Problem w/ Defining Entities in Stylesheets]

Aplogies [Re: Problem w/ Defining Entities in Stylesheets]

2003-04-03       - By JonTom Kittredge

My problem seems to have been caused by using the wrong version of
Xalan with the right version of Xerces. (I had upgraded to Xalan
2.5.D1 -- rather than 2.4.D1, as I said in my mail -- and got confused
and was using 2.4 Xalan with Xerces 2.3.0). It all seems to be fine
now.

Sorry, JonTom

      JT Kittredge
      ITA Software, Inc.
      Cambridge, Massachusetts

On 2003-04-03 at 09:38, JonTom Kittredge wrote:
>  I just upgraded to Xalan 2.4.D1 and I am getting errors on my
>  stylesheets, which worked fine with previous versions.
>  
>  The errors seem to be focused on the entity definitions we have at the
>  top of our stylesheets. For instance, if I try to run the following
>  stylesheet --
>  
>      <?xml version="1.0" encoding="utf-8"?>
>  
>      <!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp "&#160;"> ]>
>  
>      <xsl:stylesheet version="1.0"
>        xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>  
>        <xsl:template match="/"/>
>  
>      </xsl:stylesheet>
>  
>  -- I get the following errors --
>  
>      [Error] entity-test.xsl:6:52: Element type "xsl:stylesheet" must be
declared.
>      [Error] entity-test.xsl:8:28: Element type "xsl:template" must be
declared.
>  
>      <?xml version="1.0" encoding="UTF-8"?>
>  
>  If I have a more complicated stylesheet, every single xsl element is
>  reported as undeclared. If I remove the DOCTYPE   declaration, then the
>  stylesheet parses without an error.
>  
>  I believe that this DOCTYPE declaration is a perfectly XML
>  construction. Any hints on a fix this problem or another way to define
>  entities would be received gratefully. It would be a major hassle to
>  replace all uses of  "&nbsp;" with "&#160;", not just because we use
>  it in thousands of places, but because who can remember what character
>  160 is?
>  
>  Thanks, JonTom
>  
>     JT Kittredge
>     ITA Software, Inc
>     Cambridge, Massachusetts