Altova Mailing List Archives

Re: [xsl] msxml and removing parameters from a cached processor

From: "Joe Fawcett" <joefawcett@----------->
Date: 3/24/2006 1:53:00 PM
----- Original Message ----- 
From: "Emmanouil Batsis" <Emmanouil.Batsis@xxxxxxxxxxx>

To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>

Cc: "Emmanouil Batsis" <manos_lists@xxxxxxxxxxxxxx>

Sent: Friday, March 24, 2006 1:50 PM

Subject: Re: [xsl] msxml and removing parameters from a cached processor

Robert Koberg wrote:

Are you using xsl:params with default values or sometimes not passing 
params? In other words, if you do a transform with a cached processor 
where the first time you pass param 'foo=bar' and then in the next 
transform you do not send the param 'foo' you will still get the param 
'foo=bar'. Maybe I am just missing how Manos does it?

Actually the MS API does not offer anything out of the box to reset 
parameter values to their default; the reset method brings back the 
transformer to the state prior to the last transformation, but that does 
not mean it resets the params to their defaults (well, AFAIK).

Sarissa implements Mozilla's XSLTProcessor for IE but that impl does not 
include the clearParameters method (which switches the params to the 
defaults). The mechanism is mostly there so i guess i'll have to fix for 
the next release ;-)


How would that work?

Would you have to store the defaults (in a hashtable for example) when the 
setParameter was called?




These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.