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.
Numeric entity problem

Numeric entity problem

2003-09-24       - By Erik Ytterman
Reply:     1     2  

Dear All!

I'm struggling with a problem that needs to be solve as soon as
possible. Hope that you will be able to help me. I will attach parts of
the code.

I'm doing the following:

1. Recive a callback with a proper XML document.
(DocumentHandler.handleDocument())

2. Use XPath to find the element to process
(DocumentHandler.translateDocument())

3. Find the text content of this element.
(DocumentHandler.translateDocument())

4. Translate the textual content of the element.
(OpenB2BUtil.translateString())

5. An ugly hack to transform any characters except ASCII into numeric
entities. (OpenB2BUtil.etitifyIsoString())

6. Replace the textual content of the element, including numeric
entities (DocumentHandler.translateDocument())

7. Serialize the resulting DOM tree using transformers
(OpenB2BUtil.documentToStream())

Problem:

As can be seen from the code, I replace the textual content of an
element, with a string that contains numeric entities (&#253;). My
problem is that the serialization seem to translate this into
(&amp;#253;).

Questions:

1. Is this a bug in xalan, from my point of view, it should leave the
numeric entity in the text payload untouched, since it is proper XML.

2. If not, is there a way to disable this "feature" in Xalan, so that
these, perfectly legal numeric entities are let through in the
serialization

3. If not, any sugestions on how to solve the problem?

/Erik






<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Meddelande</TITLE>

<META content="MSHTML 6.00.2800.1141" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>Dear
All!</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>I'm struggling with
a problem that needs to be solve as soon as possible. Hope that
</FONT></SPAN><SPAN class=751483808-24092003><FONT face=Arial size=2>you will
be
able to help me. I will attach parts of the code.</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>I'm doing the
following:</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>1. Recive a
callback
with a proper XML document.
(DocumentHandler.handleDocument())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003></SPAN><SPAN
class=751483808-24092003></SPAN><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>2. Use XPath to
find
the element to process (DocumentHandler.translateDocument())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>3. Find the text
content of this element.
(DocumentHandler.translateDocument())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>4. Translate the
textual content of the element.
(OpenB2BUtil.translateString())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>5. An ugly hack to
transform any characters except ASCII into numeric entities.
(OpenB2BUtil.etitifyIsoString())&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>6. Replace the
textual content of the element, including numeric entities
(DocumentHandler.translateDocument())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>7. Serialize the
resulting DOM tree using transformers
(OpenB2BUtil.documentToStream())</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003></SPAN><SPAN
class=751483808-24092003></SPAN><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2>Problem:</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>As can be seen from
the code, I replace the textual content of an element, with a string
</FONT></SPAN><SPAN class=751483808-24092003><FONT face=Arial size=2>that
contains numeric entities (&amp;#253;). My problem is that the serialization
seem to translate this into (&amp;amp;#253;).&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2>Questions:</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>1. Is this a bug in
xalan, from my point of&nbsp;view, it should leave the numeric entity in the
text payload untouched, since it is proper XML.</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>2. If not, is there
a way to disable this "feature" in Xalan, so that these, perfectly legal
numeric
entities are let through in the serialization</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial size=2>3. If not, any
sugestions on how to solve the problem?</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2>/Erik</FONT></SPAN></DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=751483808-24092003><FONT face=Arial
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV></BODY></HTML>