I misunderstood the details! I use either the XalanDOMString or char* string to pass the parameters. Without code change, you would need somehow to transcode the text content of the XObjectPtr nodes to XalanDOMString(s). Then register the parameters with a new instance of XalanTransformer. Once the XSLT transformation process has started, the top-level parameters are fixed.
>From within a stylesheet, you can pass parameters to templates. These parameters are implemented as XObjectPtr nodes. I am not sure how to use XObjectPtr information outside of the XalanTransformer initialization process when preparing for a XSLT transformation. If you could share some details on how the XALANC-451 fix can be tested, I would be appreciative. Otherwise, it will not be included into the SVN repository trunk. Steven J. Hathaway > Steven, > > I hope you don't mind me asking this 'off-list' (and if you do, I won't > mind if you send a reply to this email to the xalan-dev list). > You wrote that "Top-level parameter passing into XalanTransformer works in > the CurrentSVN". I'd like to know: how did you determine that? The > reason I'm asking is we use that XALANC-451 fix, so when we decided to > update Xalan to the SVN version of around 15 March this year, I personally > added said fix and then fixed the compile errors to get it to compile. > But it would be awesome if I could get that 'hand-work' out of our Xalan > build. At least in the Xalan SVN version as it was on March 15, I'm not > seeing any XalanTransformer::setStylesheetParam member functions that > would appear to accept an XObjectPtr argument. (There are only two > setStylesheetParam member-functions, one with two const-XalanDOMString& > args, and one with two const-char* args.) Or is there a different way to > accomplish that? Or has new functionality been added to the SVN-version > after March 15? > > Sincerely, > Martin > > > -----Original Message----- > From: Steven J. Hathaway (JIRA) [mailto:xalan-dev@xml.apache.org] > Sent: Wednesday, July 06, 2011 9:35 PM > To: xalan-dev@xml.apache.org > Subject: [jira] [Commented] (XALANC-451) XalanTransformer > setStylesheetParam(key, xobject) > > > [ > https://issues.apache.org/jira/browse/XALANC-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060784#comment-13060784 > ] > > Steven J. Hathaway commented on XALANC-451: > ------------------------------------------- > > Top-level parameter passing into XalanTransformer works in the CurrentSVN. > I have used this capability with the Xalan command line executable and > other XalanTransformer based applications. > > I use the capability to pass top-level parameters into XalanTransformer > when creating the Xalan-C Version 1.11 User Guide web pages. > >> 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: xalan-dev-unsubscr...@xml.apache.org > For additional commands, e-mail: xalan-dev-h...@xml.apache.org > > > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally > privileged information. If you are not the intended recipient you are > hereby notified that any disclosure, copying, distribution or taking any > action in reliance on the contents of this information is strictly > prohibited and may be unlawful. If you have received this communication in > error, please notify us immediately by forwarding this email to > mailad...@usoft.com and then delete it from your system. > > USoft is neither liable for the proper and complete transmission of the > information contained in this communication nor for any delay in its > receipt. > --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
