RE: [xsl] SAX Transformation: Servlet returns blank XSL template

Subject: RE: [xsl] SAX Transformation: Servlet returns blank XSL template
From: "Paul Brown" <prb@xxxxxxxxxxxxx>
Date: Wed, 9 Oct 2002 23:05:45 -0400
> -----Original Message-----
> From: Bruce McDougald [mailto:bmcdougald@xxxxxxxxxxx]
>     if (tFactory.getFeature(SAXSource.FEATURE) &&
> tFactory.getFeature(SAXResult.FEATURE))

One comment that doesn't answer your question: the feature that you're after isn't either of those above.  You actually want to test SAXTransformerFactory.FEATURE (to see if the cast will succeed) and SAXTransformerFactory.FEATURE_XMLFILTER (to see if the newXMLFilter(...) methods are supported.

The problem with your servlet is in the XMLFilter.  A couple of comments:

1) Unless you're explicitly configuring the namespace properties for the driving XMLReader (and are sure that no one else is going to change them), using QName to drive logic is a Bad Idea.  For instance, with some namespace property settings, you're not even guaranteed to get a QName parameter.

2) You do not want the static on the fields in the XMLFilter.  You should use non-static fields, overload the parse(...) methods, and perform any necessary initialization there.  (This is the reason that you're getting the strange behavior on the second pass.  Look up the meaning of the static keyword in the Java language specification; section for static Fields.)

You should come on over to the SAX users list (sax-users@xxxxxxxxxxxxxxxxxxxxx) and post your XMLFilter code there for help and some pointers.

	-- Paul

 XSL-List info and archive:

Current Thread