DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=7294>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=7294 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-23 15:50 ------- (In reply to comment #0) > The current implementation of the CachedXPathAPI object creates XPath object > during the eval(), and provides a "null" ErrorHandling interface. > > // Create the XPath object. > XPath xpath = new XPath(str, null, prefixResolver, XPath.SELECT, null); > ^^^^ > This causes the XPath constructor to create a DefaultErrorHandler. The > DefaultErrorHandler creates a new PrintWriter around System.err. When there > are > lots of eval() method calls being made using the CachedXPathAPI object, there > are lots of un-needed DefaultErrorHandlers being created. Through profiling, > I > determined that 30% of the CPU utilization associated with calls to eval() > were > being attributed to creating the DefaultErrorHandlers. > > PROPOSAL: > I propose that you add functionality to either alter the constructor of the > CachedXPathAPI object to accept an ErrorHandler: > > public CachedXPathAPI(ErrorHandler); // and variations > > or add proper accessor methods to the CachedXPathAPI object: > > public ErrorHandler getErrorHandler(); > public void setErrorHandler(ErrorHandler errorHandler); > > Thanks, > Aaron yes - found that too. still valid in xalan 2.7.0. in Feb 2006. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
