Altova Mailing List Archives


Re: [xsl] XSLT parameters in TrAX filter chains?

From: Paul Tremblay <phthenry@------------->
To:
Date: 3/13/2004 10:31:00 AM
On Fri, Mar 12, 2004 at 09:42:05AM -0000, Stephen Summerfield wrote:
> Paul,
> 
> Thanks very much for that, I based my code on the example Sun give of chaining which uses XMLFilter, but yes,
> this way does look a lot easier (to write and understand). Does seem a little strange having two different
> ways of achieving the same goal in the same API - I wonder why this is, surely there is a reason(?).
> 
> Steve
> 

I'm not sure exactly, but when I looked at a thread on the saxon help
list (a sourceforge list), other posters mentioned that XMLFilter gives
you more options and flexibility, especially for exceptions (I think?).
You loose some of this flexibility when you you use SAX directly. 

This is what I gathered, anyway.

There is another website devoted to java and XML. Actually, I think it
is a book. But the author says that nothing baffles him so much as
writing filters for XML tranformations, even though they always work for
him. So I think the the API for using filters with java might be
improved a bit?

Paul

-- 

************************
*Paul Tremblay         *
*phthenry@xxxxxxxxxxxxx*
************************

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

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.