entity-encoded XML

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 ...

entity-encoded XML

entity-encoded XML

2007-02-28 - By rbaxter

Reply: 1 2 3 4 5

I have made a little progress actually. I now have an Xalan extension that
takes in the encoded data as a String and then on that String I replace all
the encoded characters with the corresponding <, >, ". The problem now is
that I need to return the data as something the stylesheet can use to select
values from. Any ideas?

Erin Harris wrote:
>
> Hi,
>
> You might want to post this to the xerces mailing list:
> j-users@(protected), as they might have some other ideas.
>
> One suggestion is to wrapper the xml file with a start and end tag and
> then parse it, providing your own ContentHandler which has the following:
>
> StringBuffer buffer = new StringBuffer();
>
> public void characters(char[] arg0, int arg1, int arg2) throws
> SAXException {
> buffer.append(arg0, arg1, arg2);
> }
>
> When I ran this against the following input:
>
> <root>
> <?xml version="1.0" encoding="utf-8"?>
> <?xml-stylesheet href="SalesToHTML.xsl"
> type="text/xsl" ?>
> 
> <SalesReport>
> <Company>XMML.com</Company>
> <Period>2001-2002</Period>
> <Sales Region="EU">50,000</Sales>
> <Sales Region="NA">150,000</Sales>
> <Sales Region="AU">10,000</Sales>
> </SalesReport>
> </root>
>
> My string buffer contained:
>
> <?xml version="1.0" encoding="utf-8"?>
> <?xml-stylesheet href="SalesToHTML.xsl"
> type="text/xsl" ?>
> 
> <SalesReport>
> <Company>XMML.com</Company>
> <Period>2001-2002</Period>
> <Sales Region="EU">50,000</Sales>
> <Sales Region="NA">150,000</Sales>
> <Sales Region="AU">10,000</Sales>
> </SalesReport>
>
> The value of the string buffer can then itself be parsed.
>
> Erin Harris
>
>
>
>
>
> rbaxter <rbaxter@(protected)>
> 27/02/2007 11:44 AM
>
> To
> xalan-j-users@(protected)
> cc
>
> Subject
> entity-encoded XML
>
>
>
>
>
>
>
> Hi, there may be a simple answer to this but I have not found anything.
>
> I have an XML file that is entity-encoded (see below) which I want to
> transform into an HTML file using Xalan. What would be the best way to
> make
> Xalan read the XML file?
>
> Sample XML file:
>
> <?xml version="1.0" encoding="utf-8"?>
> <?xml-stylesheet href="SalesToHTML.xsl"
> type="text/xsl" ?>
> 
> <SalesReport>
> <Company>XMML.com</Company>
> <Period>2001-2002</Period>
> <Sales Region="EU">50,000</Sales>
> <Sales Region="NA">150,000</Sales>
> <Sales Region="AU">10,000</Sales>
> </SalesReport>
> --
> View this message in context:
> http://www.nabble.com/entity-encoded-XML-tf3302404.html#a9186221
> Sent from the Xalan - J - Users mailing list archive at Nabble.com.
>
>
>
>

--
View this message in context: http://www.nabble.com/entity-encoded-XML
-tf3302404.html#a9207053
Sent from the Xalan - J - Users mailing list archive at Nabble.com.