modifying xalan to output invalid 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 ...

modifying xalan to output invalid XML

modifying xalan to output invalid XML

2007-05-21 - By Will Holcomb

Reply: 1 2 3

I would like to have a program that takes an input like:

<html xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="
http://www.w3.org/1999/xhtml" xml:lang="en">
<xsl:element name="auth">
<xsl:attribute name="user"><xsl:processing-instruction
name="php">print($user)</xsl:processing-instruction></xsl:attribute>
</xsl:element>
</html>

And would output a document like:

<html xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="
http://www.w3.org/1999/xhtml" xml:lang="en">
<auth user="<?php print($user) ?>" />
</html>

Can anyone here tell me how difficult this would be? What classes should I
look at modifying?

I've been looking though the codebase, but there's quite a bit of it. If I
run that template through the xslt processor currently, the processing
instruction in the attribute is simply dropped (the attribute comes out with
no value). Where does that happen? Is it when the stylesheet is compiled or
when the result is serialized?

Will Holcomb

I would like to have a program that takes an input like: <html xmlns
:xsl="<a href="http://www.w3.org/1999/XSL/Transform">http://www.w3.org/1999
/XSL/Transform</a>" version="1.0" xmlns="<a href="http://www
.w3.org/1999/xhtml">
http://www.w3.org/1999/xhtml</a>" xml:lang="en">  
<xsl:element name="auth">     <xsl
:attribute name="user"><xsl:processing-instruction name=&quot
;php">print($user)</xsl:processing-instruction></xsl:attribute
>
   </xsl:element> </html> And would output a
document like: <html xmlns:xsl="<a href="http://www.w3.org/1999
/XSL/Transform">http://www.w3.org/1999/XSL/Transform</a>" version="
1.0" xmlns="<a href="http://www.w3.org/1999/xhtml">http://www.w3.org
/1999/xhtml</a>" xml:lang="en">   <auth user="
<?php print($user) ?>" /> </html> Can anyone here
tell me how difficult this would be? What classes should I look at modifying?
 I've been looking though the codebase, but there's quite a bit
of it. If I run that template through the xslt processor currently, the
processing instruction in the attribute is simply dropped (the attribute comes
out with no value). Where does that happen? Is it when the stylesheet is
compiled or when the result is serialized?
 Will Holcomb