[
https://issues.apache.org/jira/browse/XALANC-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097731#comment-13097731
]
Steven J. Hathaway commented on XALANC-451:
-------------------------------------------
I have a review of this enhancement on my schedule. The work-around is
currently to pass a filename as a top-level parameter and convert it to a
node-set using the XPath document() function.
The enhancement in this issue provides a means to pass a node-set (i.e.
preparsed XML) as the content of a top-level parameter. I perceive the purpose
is to use and reuse the parameter (node-set) or variable (node-set) without
requiring a reparse or regeneration of an XML Fragment.
If the review passes consensus approval, it will be included. I will try to
test the capability with some custom command-line processor code which may also
become a recommendation to include the capability in the Xalan command-line
processor.
> XalanTransformer setStylesheetParam(key, xobject)
> -------------------------------------------------
>
> Key: XALANC-451
> URL: https://issues.apache.org/jira/browse/XALANC-451
> Project: XalanC
> Issue Type: Improvement
> Components: XalanC
> Affects Versions: CurrentCVS
> Reporter: Tobias Schuette
> Attachments: UseStylesheetParam.cpp, UseStylesheetParam.cpp.diff,
> XalanTransformer.cpp, XalanTransformer.cpp.diff, XalanTransformer.hpp,
> XalanTransformer.hpp.diff, foo.xsl, foo.xsl.diff
>
>
> it is not supported to pass xobject's as top level args to stylesheets
> through the XalanTransformer
> this could be easily evaluated because the underlying XSLTEngingeImpl
> supports passing in top level args as key/xobject pairs.
> attached some patches to store key/xobject pairs in XalanTransformer and a
> modified version of the UseStylesheetParam sample.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
