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.
transform collapsing Element

transform collapsing Element

2003-02-02       - By Simon Kitching
Reply:     1     2     3     4     5     6     7     8  

Hi Tim,

Just to clarify, is the following summary of the problem correct?

You have an XSL stylesheet which is intended to generate HTML output.
The original text representation of the stylesheet contains <td></td>
nodes intended for inclusion in the (html) output of the xsl
translation. However, for some reason you need to parse the stylesheet
then reserialise the stylesheet, and this process is mapping the td pair
into <td/>.

The stylesheet still works OK, right? Whether a stylesheet contains
<td/> or <td></td>, it still creates a single node in the DOM or SAX
output which is serialised as one or two tags depending on whether the
stylesheet output method is html or xml.

I gather, therefore, that you just don't like the "look" of your
reserialised stylesheet.

I don't believe that either xalan or xerces' serialiser functionality
allows you to serialise XML with some/all nodes in "split" format. Nor
do I think it terribly likely that a patch for this would be accepted,
though I am not a xerces/xalan developer - I just don't see much demand
for this.

If you really want to see <td></td> instead of <td/>, perhaps you can
post-process the serialised output? This would seem reasonably easy &
safe to do. Or maybe you should just avoid parsing/reserialising your
stylesheet...

Regards,

Simon

On Sat, 2003-02-01 at 08:08, Tim Cronin wrote:
> I still have a problem.
>
> I'm not trying to Transform xml with XSL
>
> I have a Stylesheet (xsl) loaded into a dom.
>
> I need to write the dom to a string to store it in a DB
>
> I'm using the following to convert to String
>
> public static String toString
> (
>   Document doc,
>   boolean indent
> ) throws TransformerException
> {  
>   StringWriter sw = new StringWriter();
>  
>   Transformer transformer =
> TransformerFactory.newInstance().newTransformer();
>   transformer.setOutputProperty("method", "xml");
>   transformer.setOutputProperty("omit-xml-declaration", "yes");
>   if (indent)
>   {
>     transformer.setOutputProperty("indent", "yes");
>   }
>
>   transformer.transform(new DOMSource(doc.getDocumentElement()), new
> StreamResult(sw));
>  
>   return sw.toString();
> }
>
>
> when I dump the string to system.out
> the empty <td></td> get collapsed to <td/>
>
> is there a way to stop this?
>
> -----Original Message-----
> From: Joseph Kesselman [mailto:keshlam@(protected)]
> Sent: Friday, January 31, 2003 1:05 PM
> To: xalan-j-users
> Subject: RE: transform collapsing Element
>
>
> I've lost track -- are you now OK (set the output to "html" if you don't
> want xml-style representation of empty elements), or do you still have a
> problem?
>
> ______________________________________
> Joe Kesselman  / IBM Research
>