[ http://nagoya.apache.org/jira/browse/XALANJ-1372?page=history ]
Henry Zongaro updated XALANJ-1372:
----------------------------------
Priority: Major (was: Blocker)
> Performance improvement ideas wrt loading JAXP Factories and DTMManager
> -----------------------------------------------------------------------
>
> Key: XALANJ-1372
> URL: http://nagoya.apache.org/jira/browse/XALANJ-1372
> Project: XalanJ2
> Type: Bug
> Components: JAXP
> Versions: CurrentCVS
> Environment: Operating System: Other
> Platform: Other
> Reporter: Ilene Seelemann
>
> 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?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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]
