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.
Only one -PARAM allowed on the commandline?

Only one -PARAM allowed on the commandline?

2003-01-22       - By zongaro@(protected)
Reply:     1     2     3     4  

Hi Christophe,

    I don't seem to be able to reproduce your problem with Xalan-J 2.4.1
or the latest code from CVS.  For example:

$ java org.apache.xalan.xslt.Process -IN blah.xml
                                    -XSL param.xsl
                                    -PARAM param1 toto
                                    -PARAM param2 titi

produces the following output for me:

<?xml version="1.0" encoding="UTF-8"?>
<param1>toto</param1><param2>titi</param2>


    I don't have a copy of Xalan-J 2.4.0 handy, so I'm not sure whether
this is a problem that was fixed since that release.

Thanks,

Henry
------------------------------------------------------------------
Henry Zongaro      Xalan development
IBM SWS Toronto Lab   Tie Line 969-6044;  Phone (905) 413-6044
mailto:zongaro@(protected)




Christophe Galerne <christophegalerne@(protected)>
01/21/2003 06:22 PM


       To:     xalan-j-users@(protected)
       cc:
       Subject:        Only one -PARAM allowed on the commandline?



Hi,

Given this stylesheet:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                version="1.0">

<xsl:param name="param1"/>
<xsl:param name="param2"/>

<xsl:template match="/">
                <param1><xsl:value-of select="$param1"/></param1>
                <param2><xsl:value-of select="$param2"/></param2>

</xsl:template>

</xsl:stylesheet>

This invocation of xalan:
java
                -Djava.endorsed.dirs="d:\xalan-j_2_4_0\bin"
                org.apache.xalan.xslt.Process
                -IN xml/whatever.xml
                -XSL xsl/param.xsl
                -PARAM param1 toto
                -PARAM param2 titi

produces this result:
<?xml version="1.0" encoding="UTF-8"?>
<param1>toto</param1><param2/>

and this invocation:
java
                -Djava.endorsed.dirs="d:\xalan-j_2_4_0\bin"
                org.apache.xalan.xslt.Process
                -IN xml/whatever.xml
                -XSL xsl/param.xsl
                -PARAM param2 titi

this result:
<?xml version="1.0" encoding="UTF-8"?>
<param1/><param2>titi</param2>

So it looks like only one parameter is allowed on the command line.

However the documnentation in 'commandline.html' states:
'
To set stylesheet parameters from the command line, use
java org.apache.xalan.xslt.Process -PARAM name value
'

This is really a detail but maybe the doc should not imply that
multiple parameters can be specify.

Thanks,
Christophe