Altova Mailing List Archives

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

From: "Ant&#xF3;nio Mota" <amsmota@--------->
Date: 3/23/2006 6:10:00 PM
hmmm, don't remember if i allways pass the parameter or not.... I'll
test your situation using Sarissa when i'm back to my office, perhaps

Whto do you mean with

>  I haven't tried using Sarissa. I don't think it can write a full
> page into a iframe/frame??

Sarissa is just Javascript, if you can do it wuth Javascript you can
do ir with Sarissa...

On 23/03/06, Robert Koberg <rob@xxxxxxxxxx> wrote:
> Antsnio Mota wrote:
> > That's strange, i've never noticed that problem... Did you try the
> > equivalente operation in Firefox? And using the cross-browser library
> > Sarissa? (that's what i use)...
> Hi,
> It works in firefox because the processor object has a clearParameters
> method. I haven't tried using Sarissa. I don't think it can write a full
> page into a iframe/frame??
> I just took a look through Sarissa's source to see how it is handled
> there. I don't see anything that removes/resets a cached processor's
> parameters (I am probably wrong).
> 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?
> best,
> -Rob
> >
> > On 23/03/06, Robert Koberg <rob@xxxxxxxxxx> wrote:
> >> Hi,
> >>
> >> Is there some way to remove parameters from a cached
> >> 'new ActiveXObject( 'Msxml2.XSLTemplate.3.0' )' XSL processor in
> >>
> >> I see there is a reset method on the processor object, but the docs say
> >> that the method resets it to the state prior to the transform. But the
> >> params were set prior to the transform and in fact the rest method does
> >> not remove them.
> >>
> >> I currently send a param array to a transformation function. I loop
> >> through it to add params -> then transform -> then loop through to set
> >> all the params to an empty string. This is not good mainly because there
> >> might be default parameter values in the XSL. I could walk the XSL's DOM
> >> to find the default param values, but it seems like overkill and thought
> >> I would ask if I am missing something.
> >>
> >> Thanks,
> >> -Rob


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.