Yes, I know this is a loaded question <g>, but we've found that factory models are often causing SIGNIFICANT performance hits on object creation, especially when the factory has to defer to looking for property files, getResourceAsStream(), and the classloader's handling of class.forName() and newInstance(), getResourceAsStream.
We were also wondering why each package seems to have its own ObjectFactory implementation, with mostly the same code (and most of the code appears to be unused). As a specific optimization example, DTMManager uses ObjectFactory.createObject(), but when would anything other than DTMManagerDefault be used? Thus far, this is the only one we've found in Xalan that can be optimized. Setting system properties to pre-empt this searching has a ***PROFOUND*** positive effect on performance, but it isn't clear other than trial and error what/where all of the properties are located (in both Xalan and Xerces, for that matter). Is there any documentation on the various factories and their defaults? The only one we could find that would actually defer to Many thanks, and happy holidays to all! Rick Bullotta CTO Lighthammer Software (http://www.lighthammer.com) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
