You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by John Gentilin <ge...@eyecatching.com> on 2002/09/28 00:06:58 UTC
Generating XMLSS (MS Excel) files
I have been using Xalan to generate XMLSS compliant file
for a while now and in the last few weeks I noticed a major
performance change, on the order of 6X slower. Thought for
sure it was due to one of my latest DB changes but come to
find out, the problem goes away if I am not connected to the
net. My guess is that the namesspace declarations for the XMLSS
elements is pulling in a DTD that is causing problems. Has anyone
experienced this type of problem. ??
Performance change goes from ~30 Sec to 3-5 Min
Regards
John G
Here is my stylesheet declaration.
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xalan="http://xml.apache.org/xalan"
xmlns:java="http://xml.apache.org/xslt/java"
xmlns:html="http://www.w3.org/TR/REC-html40"
xmlns:sql="org.apache.xalan.lib.sql.XConnection"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns="urn:schemas-microsoft-com:office:spreadsheet"
extension-element-prefixes="sql" exclude-result-prefixes="xalan java">
--
--------------------------------------
John Gentilin
Eye Catching Solutions Inc.
18314 Carlwyn Drive
Castro Valley CA 94546
Contact Info
gentijo@eyecatching.com
Ca Office 1-510-881-4821
NJ Office 1-732-422-4917
Re: Generating XMLSS (MS Excel) files
Posted by John Gentilin <ge...@eyecatching.com>.
Oops never mind my bad... My original assumption was correct, it is a
database problem.
Problem is when I am connected to the net, I am having trouble resolving the
name of
my computer jglaptop, if I disconnect from the net or change my JDBC url to
localhost,
problem solved.
Sorry for the confusion
John G
Joseph Kesselman wrote:
> Simpler for us if it's a stand-alone "run these documents" test; that
> avoids dependencies on anything but Xalan, and it's a bit easier to muck
> with the testcase if we need to in order to explore the problem.
>
> ______________________________________
> Joe Kesselman / IBM Research
Re: Generating XMLSS (MS Excel) files
Posted by Joseph Kesselman <ke...@us.ibm.com>.
Simpler for us if it's a stand-alone "run these documents" test; that
avoids dependencies on anything but Xalan, and it's a bit easier to muck
with the testcase if we need to in order to explore the problem.
______________________________________
Joe Kesselman / IBM Research
Re: Generating XMLSS (MS Excel) files
Posted by John Gentilin <ge...@eyecatching.com>.
I will create one. I could do it one of two ways, 1) build a source document
out
of the data I have or 2) create a similar SS to the one I am using the
utilizing the
SQL Example data which assumes that you have InstandDB configured. What
sounds better ??
Joseph Kesselman wrote:
> If there's "no source document", then neither Xalan nor Xerces should be
> trying to dereference namespace URIs in it... And we don't dereference
> them in the stylesheet, or shouldn't be doing so.
>
> I can't think of anything that would cause this effect. Needs more
> research. I've sorta got my hands full right at the moment, so if someone
> else wants to start investigating pls. be my guest -- otherwise I'll try
> to take a look at it in a week or so.
>
> I've forgotten -- John, did you post a testcase into Bugzilla?
>
> ______________________________________
> Joe Kesselman / IBM Research
--
--------------------------------------
John Gentilin
Eye Catching Solutions Inc.
18314 Carlwyn Drive
Castro Valley CA 94546
Contact Info
gentijo@eyecatching.com
Ca Office 1-510-881-4821
NJ Office 1-732-422-4917
Re: Generating XMLSS (MS Excel) files
Posted by Joseph Kesselman <ke...@us.ibm.com>.
If there's "no source document", then neither Xalan nor Xerces should be
trying to dereference namespace URIs in it... And we don't dereference
them in the stylesheet, or shouldn't be doing so.
I can't think of anything that would cause this effect. Needs more
research. I've sorta got my hands full right at the moment, so if someone
else wants to start investigating pls. be my guest -- otherwise I'll try
to take a look at it in a week or so.
I've forgotten -- John, did you post a testcase into Bugzilla?
______________________________________
Joe Kesselman / IBM Research
Re: Generating XMLSS (MS Excel) files
Posted by John Gentilin <ge...@eyecatching.com>.
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
gentijo@eyecatching.com
Ca Office 1-510-881-4821
NJ Office 1-732-422-4917
Re: Generating XMLSS (MS Excel) files
Posted by Joseph Kesselman <ke...@us.ibm.com>.
>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