From: Daniel Parker <danielp@wi...> - 2001-10-02 14:57:51
Why do you need to reuse the transformer object in this way? - all of your
problems seem to stem from this. Is there any reason why you cannot create
a new transformer object for each transformation? If your need is to cache
the principal document, just use the identity transform to transform it a
DOMResult, extract the node, and create a DOMSource, which you can reuse
> ----- Original Message -----
> From: "Oliver Becker" <obecker@...>
> To: <saxon-help@...>
> Sent: Tuesday, October 02, 2001 10:15 AM
> Subject: [saxon] changing parameters
> > using the TrAX API, I can set global parameters via the setParameter
> > in javax.xml.transform.Transformer. This works only once.
> > Background: I have a transformer object on server side that should be
> > instantiated once and used for several transformations. The result of
> > the transformation is also dependent from an object state on server
> > How to retrieve this state?
> > I wanted to (mis)use the document function for retrieving such a state.
> > Because XSLT enforces the returned root node to be the same for
> > URIs, saxon obviously caches the belonging document. The next idea was
> > use document($source) inside of my stylesheet and modify the source
> > for different runs of the transformation. But without success.
> > Any ideas? Should I explicitely call a private extension function
> > of document?