Mode processing question

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

Mode processing question

Mode processing question

2005-10-12 - By Erin Harris

Reply: 1 2 3

Do you want to be able to change the mode from the command line or from
Java? If so you could try something like the following where the
parameter "mode" can be set through the PARAM command line option or by
calling Transformer.setParameter(String name, Object value) from Java:

<xsl:param name="mode" select="'A'"/>

<xsl:template match="/">
<xsl:choose>
<xsl:when test="$mode='A'">
<xsl:apply-templates mode="A"/>
</xsl:when>
<xsl:otherwise>
<xsl:apply-templates mode="B"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

Erin Harris

"Matei Florescu" <matei.florescu@(protected)>
10/12/2005 08:49 AM

To
xalan-j-users@(protected)
cc

Subject
Mode processing question

Hello,

I have a XSL stylesheet with templates defined in multiple modes. How
can I get
Xalan to process templates with single mode in a transformation?
Ex. I have templates with mode="A" and mode="B", and I want to apply only
those
with mode="A".

--
Matei Florescu

 Do you want to be able to change the
mode from the command line or from Java?  If so you could try something
like the following where the parameter "mode" can be set through
the PARAM command line option or by calling Transformer.setParameter(String
name, Object value) from Java:
 
 <xsl:param name="mode" select=
"'A'"/>
 
 <xsl:template match="/">
     <xsl:choose>
         <xsl:when
test="$mode='A'">
            
<xsl:apply-templates mode="A"/>
         </xsl:when>
         <xsl:otherwise
>
            
<xsl:apply-templates mode="B"/>
         </xsl:otherwise
>
     </xsl:choose>
 </xsl:template>
 
 
Erin Harris 
 

 
 
 
<table width=100%>
<tr valign=top>
<td width=40%>"Matei Florescu"
<matei.florescu@(protected)> 
10/12/2005 08:49 AM
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right>To</div>
<td valign=top>xalan-j-users@(protected)
<tr>
<td>
<div align=right>cc</div>
<td valign=top>
<tr>
<td>
<div align=right>Subject</div>
<td valign=top>Mode processing question<
/table>
 
<table>
<tr valign=top>
<td>
<td></table>
 </table>
 
 
 <tt>Hello, 
 
 I have a XSL stylesheet with templates defined in multiple modes.
How can I get 
Xalan to process templates with single mode in a transformation? 
Ex. I have templates with mode="A" and mode="B", and
I want to apply only those 
with mode="A". 
 
-- 
Matei Florescu 
</tt>