Conditional statements in XSLT

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

Conditional statements in XSLT

Conditional statements in XSLT

2006-03-24 - By Higino Silva

Reply: 1 2

Hi all,

I'm using Xalan J, and though I don't have a particular problem with the
implementation of Xalan I'm having troubles implementing one of the
requirements for our project, I'm even not sure if is at all possible
to do it applying only XSL transformations.

Can anyone advise me on this one:

I have the following input xml document:

<RESULT>

<PARAMETERS>

<CYCLE>

<ENDDATE>20060215</ENDDATE>

</CYCLE>

<FILE><CHECK/></FILE>

</PARAMETERS>

<OUTPUT>

<FILE>b</FILE>

<FILENAME>E:\ftphome\vodafone\xml\CC20060215S50.XML</FILENAME>

</OUTPUT>

</RESULT>

Now, the resulting xml should have the FILE and FILENAME tags belonging
to OUTPUT element transferred to PARAMETERS element, which I can do with
no effort at all with the following template:

<--! Coy input node to the output -->
<xsl:template match="*">

<xsl:copy>

<xsl:apply-templates />

</xsl:copy>

</xsl:template>

<xsl:template match="OUTPUT"></xsl:template> 

<--! Copy output nodes to Parameters element -->

<xsl:template match="/RESULT/PARAMETERS">

<xsl:copy>

<xsl:copy-of select="/RESULT/OUTPUT/*" />

<xsl:apply-templates />

<xsl:copy>

</xsl:template>

The tricky thing here, is that if the FILE/FILENAME tag (or any tag
under OUTPUT) exists under PARAMETERS, then the tag under PARAMETERS
should be overwritten by correspondent OUTPUT tag. In this case the
correct output should be the following:

<RESULT>

<PARAMETERS>

<CYCLE>

<ENDDATE>20060215</ENDDATE>

</CYCLE>

<FILE>b</FILE>

<FILENAME>E:\ftphome\vodafone\xml\CC20060215S50.XML</FILENAME>

</PARAMETERS>

</RESULT>

I would much appreciate some help, and since I'm not sure I'm using the
right mailing list, please accept my apologies and please guide to a
correct one.

Many many thanks

Higino Silva

AVISO

Esta mensagem e quaisquer anexos seus podem conter informacao confidencial para
uso exclusivo do destinatario. Cabe ao destinatario assegurar a verificacao de
virus e outras medidas que assegurem que esta mensagem nao afecta os seus
sistemas. Se nao for o destinatario, nao devera usar, distribuir ou copiar este
e-mail, devendo proceder a sua eliminacao e informar o emissor. E estritamente
proibido o uso, a distribuicao, a copia ou qualquer forma de disseminacao nao
autorizada deste e-mail e seus anexos. Obrigado.

DISCLAIMER
This e-mail and its attachments may contain confidential information for
exclusive use of its recipient. It is your responsibility to carry out
appropriate virus and other checks to ensure that this message and any
attachments do not affect your systems / data. If you are not the intended
recipient you must not use, distribute or reproduce this e-mail and you must
notify the sender and delete the entire email. Any unauthorized use,
dissemination, distribution or copying of this message and its attachments is
strictly prohibited. Thank You.

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft
-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn
:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office
:powerpoint" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns="http:
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>

</style>

</head>

<body lang=PT link=blue vlink=purple>

<div class=Section1>

Hi all,<o:p></o:p
>

<o:p> </o:p>


I’m using Xalan J,
and though I don’t have a particular problem with the implementation of
Xalan I’m having troubles implementing one of the requirements for our
project,  I’m even not sure if is at all possible to do it applying
only XSL transformations.<o:p></o:p>

Can anyone advise me on
this one:<o:p></o:p>

 <o:p></o:p>

I have the following input
xml document:<o:p></o:p>

<RESULT><o:p></o:p>

  <PARAMETERS>
<o:p></o:p>

    <CYCLE><o:p></o:p>

     
<ENDDATE>20060215</ENDDATE>
<o:p></o:p>

    </CYCLE><o:p></o:p>

    <FILE><CHECK/></FILE><o:p></o:p>

  </PARAMETERS><o:p></o:p>

  <OUTPUT><o:p></o:p>

    <FILE>b</FILE><o:p></o:p>

    <FILENAME>E:\ftphome\vodafone\xml
\CC20060215S50.XML</FILENAME><o:p></o:p>

  </OUTPUT><o:p></o:p>

</RESULT><o:p></o:p>

<o:p> </o:p>

Now, the resulting xml
should have the FILE and FILENAME tags belonging to OUTPUT element transferred
to
PARAMETERS element, which I can do with no effort at all with the following
template:<o:p></o:p>

<--! Coy input node to
the output --> 
<xsl:template match="*"><o:p></o:p>


<xsl:copy>
<o:p></o:p>

<xsl:apply-templates
/><o:p></o:p>


</xsl:copy>
<o:p></o:p>

</xsl:template><o:p><
/o:p>

<xsl:template
match="OUTPUT"></xsl:template> <o:p></o:p>

<--! Copy output nodes to
Parameters element --><o:p></o:p>

<xsl:template
match="/RESULT/PARAMETERS"><o:p></o:p>


<xsl:copy>
<o:p></o:p>

<xsl:copy-of
select="/RESULT/OUTPUT/*" /><o:p></o:p>

<xsl:apply-templates
/><o:p></o:p>


<xsl:copy>
<o:p></o:p>

</xsl:template><o:p><
/o:p>

<o:p> </o:p>

The tricky thing here, is
that if the FILE/FILENAME tag (or any tag under OUTPUT) exists under
PARAMETERS, then the tag under PARAMETERS should be overwritten by
correspondent OUTPUT tag. In this case the correct output should be the
following:<o:p></o:p>

<RESULT><o:p></o:p>

  <PARAMETERS>
<o:p></o:p>

    <CYCLE><o:p></o:p>

     
<ENDDATE>20060215</ENDDATE>
<o:p></o:p>

    </CYCLE><o:p></o:p>

   <FILE>b</FILE><o:p></o:p>

   <FILENAME>E:\ftphome\vodafone
\xml\CC20060215S50.XML</FILENAME><o:p></o:p>

  </PARAMETERS>
<o:p></o:p>

</RESULT><o:p></o:p>

<o:p> </o:p>

I would much appreciate
some help, and since I’m not sure I’m using the right mailing list,
please accept my apologies and please guide to a correct one.<o:p></o:p>


<o:p> </o:p>

Many many thanks<o:p></o
:p>

Higino Silva<o:p></o:p>

</div>

 AVISOEsta mensagem e quaisquer anexos seus podem
conter informação confidencial para uso exclusivo do destinat
ário. Cabe ao destinatário assegurar a verificação
de vírus e outras medidas que assegurem que esta mensagem n&atilde
;o afecta os seus sistemas. Se não for o destinatário, não
deverá usar, distribuir ou copiar este e-mail, devendo proceder à
 sua eliminação e informar o emissor. É estritamente
proibido o uso, a distribuição, a cópia ou qualquer forma
de disseminação não autorizada deste e-mail e seus anexos.
Obrigado. DISCLAIMERThis e-mail and its
attachments may contain confidential information for exclusive use of its
recipient. It is your responsibility to carry out appropriate virus and other
checks to ensure that this message and any attachments do not affect your
systems / data. If you are not the intended recipient you must not use,
distribute or reproduce this e-mail and you must notify the sender and delete
the entire email. Any unauthorized use, dissemination, distribution or copying
of this message and its attachments is strictly prohibited. Thank You.</body>

</html>