[richfaces-issues] [JBoss JIRA] Updated: (RF-10413) TemplateEncoderRendererbase always uses Tidy Parser, even if NEKO defined in default parser

TemplateEncoderRendererbase always uses Tidy Parser, even if NEKO defined in default parser ------------------------------------------------------------------------------------------- Key: RF-10413 URL: https://issues.jboss.org/browse/RF-10413 Project: RichFaces Issue Type: Bug Security Level: Public(Everyone can see) Components: component Affects Versions: 3.3.3.Final Environment: Windows XP SP3, 32-bit; Linux 2.6.18, 32bit Reporter: Neil Buesing Assignee: Nick Belaevski Labels: Parser Fix For: 3.Future In an attempt to improve performance (as observed with JProfiler) switched from using Tidy parser to the NEKO parser. In doing so, no changes were observed in the TemplateEncoderRendererBase class (which ContextMenuRendererBase inherits) that we are using for our context sensitive menus. In a 12 second response test, over 8 seconds appears to be happening within TemplateEncoderRendererBase.writeScriptBody(). It appears, that method is hard-coded to use the Tidy Parser. It also appears it reads the tidy.properties file on every call to the method. I was hoping this would use the NEKO parser when defined as the default parser within our web.xml file.