This question is very Saxon-specific, and would be better asked on the
saxon-help list at Sourceforge.
Importing the same module at many different import precedences can lead
to serious performance problems and is quite unnecessary, which is why
Saxon introduced this warning. In fact, at the same time I changed the
implementation so the performance impact isn't quite as bad as it was
before, but it can still seriously increase the complexity of searching
for the correct match for a template rule.
You can customize the way that errors and warnings are output by using
your own ErrorListener. If you want your application to behave
differently depending on what errors and warnings have been reported I
would have thought you would want your own ErrorListener, rather than
trying to parse the log file.
Michael Kay
Saxonica
On 01/03/2011 22:42, Graydon wrote:
Hi --
Saxon 9.3 warns on multiple imports/includes.
I've got a production environment where the test for "did that work?" is
the XSLT transformation log being empty. There is considerable
resistance to the idea of changing this for a "smarter" test that seeks
to examine what's in the log. There is also a desire to move the
production toolchain to 9.3, partially out of a policy to avoid
version-specific dependencies for software and partially because some
other parts of the process are seeing performance improvements.
Unfortunately I've also got 30+ XSLT files that are more or less
inescapable for both sanity (hundreds of templates) and because
management insists on a fine level of granularity so multiple
programmers can work in parallel. The actual "deal with path matches"
files all import the "get the infrastructure here" file which pulls in
the files with the common functions, standard definitions, and so on.
This is required so that the individual files will validate, and it is a
requirement that the individual files validate.
There's also a single chain of include statements that pulls the whole
thing into the template that calls all of this for processing purposes.
So I've got multiple imports, they're on purpose, and I
can't figure out how to make them go away.
I have, so far, been unable to find anywhere that describes how to turn
the warn-of-multiple-imports-or-includes feature in Saxon 9.3 off.
I would greatly appreciate any suggestions anyone's got, either for how
to handle the situation so the individual XSLT files can be validated
without multiple imports/includes (can one do something clever with
catalogs?) or how to turn the feature off in Saxon 9.3.
Thanks!
Graydon
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--