Hi Todd,
        I'm writing this to you as I see from xml.apache.org that you are
responsible for the JAXP side of things.
Im having difficulties compiling a translet/Templates object. It works fine
as long as I dont use:

System.setProperty("javax.xml.transform.TransformerFactory","org.apache.xala
n.xsltc.runtime.TransformerFactoryImpl");

If I use this line the system seems unable to fins any of my xsl files to
compile. It messes up the paths or something. Do you kow what could be
wrong?

thanks,

Paul.

-----Original Message-----
From: G. Todd Miller - XML Tech Ctr - Development
[mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 6:43 PM
To: [EMAIL PROTECTED]
Subject: XMLFilter chaining question...




Question: In the sample program UseXMLFilters.java (located in
 xml-xalan/java/samples/UseXMLFilters) it appears that 3 XMLFilters
 (filter1, filter2, and filter3 in diagram) are being chained together
 into a pipeline, a Serializer is plugged into filter3 as a
 ContentHandler, and an XMLReader is plugged into filter1 as a parent.
 And then, the input XML document is being feed into the *last*
 filter in the pipeline:


  XMLReader       foo1.xsl   foo2.xsl   foo3.xsl          foo.xml
   |   ^             |          |         |                |
   |   |             |          |         |                |
   |   |             v          v         v                |
   |   |  xml   +----------+----------+-----------+  xml   |
   |   +----<---|          |          |           |<-------+
   |            | filter1  |  filter2 |  filter3  |
   +----->------|          |          |           |------> Serializer
   sax evts     +----------+----------+-----------+

 So the app program calls filter3.parse("foo.xml"); filter3 turns around
 and calls filter2.parse("foo.xml"); filter2 turns around and calls
 filter1.parse("foo.xml"); filter1 finally hands off the xml doc to
 an XMLReader, the reader parses the doc and produces SAX parser
 events. The parser events are input to filter1; transformed; output
 of transform is sent to filter2; transformed; output to filter3
 transformed and then output to Serializer.

 (If I am correct in this analysis) then the question: why have the
 Xml input doc be 'forwarded' from the end of the pipe to the beginning,
 to be read?   Why not design the pipeline such as:


                 foo1.xsl   foo2.xsl   foo3.xsl
   foo.xml           |          |         |
      |              |          |         |
      |              v          v         v
      |         +----------+----------+-----------+
      v         |          |          |           |
  XMLReader---->| filter1  |  filter2 |  filter3  |------> Serializer
                |          |          |           |
                +----------+----------+-----------+


Thanks for any insights/corrections to this,

-Todd


=======================================================================
G. Todd Miller                        Sun Microsystems Computer Company
Software Systems Engineer             2 Network Drive, MS UBUR02-201
GE&IS XML Tech Center                 Burlington, MA 01803-0903
                                      781 442-0176
                                      781 442-1437 (fax)
                                      [EMAIL PROTECTED]


Reply via email to