 |
 |
 |
I've experienced these empty divs before as well. all you need to do is
somehting like this:
<div id="something">
<xsl:comment>keep this div not empty</xsl:comment>
</div>
and that should solve your problem of a self-closing element.
this way, you do not need to change your <xsl:output> from xml to html.
you can keep it:
<xsl:output method="xml">
to retain xhtml formatting.
dale
-----Original Message-----
From: A D [mailto:hopethisisstillthere@xxxxxxxxx]
Sent: 02 June 2007 13:06
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] XSL transformation removing closing tag for empty div
Hi All,
I have a xsl which has an empty div:
<div class="somehting"></div>
I fill this div on the client side using javascript. Now, I
make an Ajax call and on the server side, I do transformation
in such a way that I get XML back as response to the Ajax
call. For this, I set the servlet response content type to be
text/xml. In doing so, the output of the transformation does
not contain the closing tag i.e it is changed to <div
class="something"/> . I would want it to keep the closing
tag. How can I achieve this?
Thanks in advance,
A D
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |