Stefan,
Thanks for your reply!
>I use SilverStream 3.73 and Xalan and it works well.
Glad to hear it! Gives me hope that it is something stupid I've done
which is causing the delays. I'm using 3.7.4 so I guess I could go back
to 3.7.3 and see if that makes a difference.
>You should check, whether you'll get the Xalan-Transformer-Factory or
>another by printing the full qualified classname with:
>System.out.println(tFactory.getClass().getName());
This returns org.apache.xalan.processor.TransformerFactoryImpl
Is that the classname I should be seeing?
>I guess it depends on Properties, wich
Transformerfactory-Implementation >you get. If you don't get Xalans
TF-Implementation, you may swap some >libaries in the AGClasspath or
change Properties. You can force the VM to >take the right TF-Impl by
using Class-ForName.
>Another point maybe that the Server gets confused by setting the
content->type of the outputstream. If the Stylesheet sets the
content-type (via >xsl:method) and the encoding it's not set twice if
you omit
>res.setContentType("text/html; charset=UTF-8");
I commented out that line in my code but saw the same result.
>BTW. Why do you use // instead of / for URLs ?
I shouldn't have - I was thinking I needed to escape / but I don't.
However, things seemed to run either way.
Thanks again for your help!
Tom
