Steven, I regret to inform you that it would totally not help you (or anyone else not in USoft) to know how we tested fix XALANC-451. Basically it came down to executing a command that that causes USoft Developer to try to make an XSL-transform... and then verifying that no crash occurred, that our automated tests succeeded, that the transformed documents are correct and things like that. The real functionality testing wasn't even done by me (I'm am not an XML or XSL expert; I'm just the guy who built 3rd party libraries such as Xerces & Xalan for our more recent porting efforts) ...
Sincerely, Martin -----Original Message----- From: shath...@e-z.net [mailto:shath...@e-z.net] Sent: Saturday, July 09, 2011 2:12 AM To: xalan-dev@xml.apache.org Subject: RE: [jira] [Commented] (XALANC-451) XalanTransformer setStylesheetParam(key, xobject) Martin, I'm glad that you have success in using this capability. The attached files were very helpful for review. I'm surprised that more extensive review was not performed by the old Xalan team. The code example operates similar to using the XPath document function, but uses top-level parameters with nodeset values referencing preparsed XML documents. The ability to use preparsed XML document fragments multiple times within a transformation can have its performance benefits. The example only tested a single XObjectPtr instance. A follow-up capability that should be tested is whether the XObjectPtr parameter value is sufficiently free of side-effects so it can be used multiple times within a single XSLT stylesheet. I will try to provide example documentation so this capability can be integrated into the product for general use. I will also try to build some good tests for documentation purposes. Sincerely, Steven J. Hathaway > 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 >> >> --------------------------------------------------------------------- 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
