For this particular instance, there is no real source document just an
empty root element. The data is being produced via the SQL Extension
which produces the XMLSS output. While the transformation is running,
there is a decent amount of net activity. Although I am basing that on the
little activity indicator in the systray. The goofy thing is, I have been
using
this code for months now, and I have only noticed the performance drop
in the last few weeks. I have two Xalan configs 3.2.1 & current CVS
both exhibit the same behavior The Xalan I/O are both StreamSource's.
-John G
Joseph Kesselman wrote:
> >My guess is that the namesspace declarations for the XMLSS
> >elements is pulling in a DTD that is causing problems
>
> Xalan itself should never be attempting attempt to dereference XML
> Namespace URIs. As far as I know, they _should_ be treated strictly as
> magic strings... unless something we're using to validate their syntax has
> decided to also try to look them up on the network, which would be rather
> rude.
>
> Are you sure there isn't a DTD reference in (one of) your source
> document(s)? We do normally run the parser in validating mode, since XSLT
> wants to know about things like IDs, so that definitely could be trying to
> hit the wire.
>
> ______________________________________
> Joe Kesselman / IBM Research
--
--------------------------------------
John Gentilin
Eye Catching Solutions Inc.
18314 Carlwyn Drive
Castro Valley CA 94546
Contact Info
[EMAIL PROTECTED]
Ca Office 1-510-881-4821
NJ Office 1-732-422-4917
