I'm not sure if that is the thread I intended it to be.
But just to do some self advertisment or to explain what
our classes do beyond the hashtable in SaxonServlet:

It is an finite memory LRU-Cache for Template instances,
that knows when to reread a Template object when the 
underlying file system objects (either the basic file
or any includes or imports). Attached to each Template
there is a pool of Transformer objects to safe the
	template.newTransformer() 
calls. It seems that those calls are costly. The pooling 
made those minor difficulties, since you need to call a 
 	transformer.clearParameters()
before you can rewrite allready written parameters via
	transformer.setParameter(...)
And I simply wondered if the behaviour "Parameters 
cannot be rewritten" is intended and why.

If you have some of those infinite memory engines left,
I'd take a dozen, unless those are Turing Machines, those
are to hard to program.

Frank

> -----Ursprüngliche Nachricht-----
> Von: Johannes Döbler [mailto:jd@xxxxxxxxxxxxxx]
> Gesendet am: Sonntag, 13. Mai 2001 15:02
> An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Betreff: RE:  JAXP Transformer contract
> 
> 
> >I'm not sure what you mean by that: TrAX is quite specific that the
> >Templates object is thread-safe. Also, the JAXP 1.1 
> transformation API was
> >defined with the benefit of experience from existing XSLT 
> implementations,
> >but it didn't follow any implementation slavishly.
> >
> >Mike Kay
> 
> Taking a second look at your SaxonServlet.java I realized 
> that I somewhat 
> missed the point about what you are doing with the hashtable 
> cache so my 
> comment about threadsafety was not appropriate.
> 
> Johannes
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list