The following issue has been updated:
Updater: Brian Minchau (mailto:[EMAIL PROTECTED])
Date: Sat, 4 Sep 2004 9:37 AM
Changes:
assignee changed from Xalan Developers Mailing List
description changed from We should go through the code and determine if
we are calling newInstance() more
than necessary (for SAXParserFactory and DocumentBuilderFactory) on a single
Transformer object. Each call can be expensive if jars are searched for the
implementation class. Can we cache these classes anywhere?
I also have questions about the factory finder code for DTMManager
implementations:
* Shouldn't we update this code to be consistent with the latest updates to the
factory finder routines in JAXP code (from xml-commons)?
* Why are we searching in jaxp.properties for the name of the DTMManager
implementation? Would this really be an appropriate place for a user to set
this property?
* Xerces has a xerces specific properties file (xerces.properties)that it looks
for in a JDK installation (to avoid going through the classpath search.) See
org.apache.xerces.util.ObjectFactory. Should we have a similar file for Xalan? to We
should go through the code and determine if we are calling newInstance() more
than necessary (for SAXParserFactory and DocumentBuilderFactory) on a single
Transformer object. Each call can be expensive if jars are searched for the
implementation class. Can we cache these classes anywhere?
I also have questions about the factory finder code for DTMManager
implementations:
* Shouldn't we update this code to be consistent with the latest updates to the
factory finder routines in JAXP code (from xml-commons)?
* Why are we searching in jaxp.properties for the name of the DTMManager
implementation? Would this really be an appropriate place for a user to set
this property?
* Xerces has a xerces specific properties file (xerces.properties)that it looks
for in a JDK installation (to avoid going through the classpath search.) See
org.apache.xerces.util.ObjectFactory. Should we have a similar file for Xalan?
environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
priority changed to Blocker
Component changed to JAXP
Component changed from Xalan
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XALANJ-1372?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XALANJ-1372
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XALANJ-1372
Summary: Performance improvement ideas wrt loading JAXP Factories and DTMManager
Type: Bug
Status: Unassigned
Priority: Blocker
Project: XalanJ2
Components:
JAXP
Versions:
CurrentCVS
Assignee:
Reporter: Ilene Seelemann
Created: Fri, 20 Dec 2002 8:32 PM
Updated: Sat, 4 Sep 2004 9:37 AM
Environment: Operating System: Other
Platform: Other
Description:
We should go through the code and determine if we are calling newInstance() more
than necessary (for SAXParserFactory and DocumentBuilderFactory) on a single
Transformer object. Each call can be expensive if jars are searched for the
implementation class. Can we cache these classes anywhere?
I also have questions about the factory finder code for DTMManager
implementations:
* Shouldn't we update this code to be consistent with the latest updates to the
factory finder routines in JAXP code (from xml-commons)?
* Why are we searching in jaxp.properties for the name of the DTMManager
implementation? Would this really be an appropriate place for a user to set
this property?
* Xerces has a xerces specific properties file (xerces.properties)that it looks
for in a JDK installation (to avoid going through the classpath search.) See
org.apache.xerces.util.ObjectFactory. Should we have a similar file for Xalan?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
