3 Replies Latest reply on May 29, 2008 9:45 AM by Mike Hanafey

    Best practice for org.ajax4jsf.xmlparser

    Mike Hanafey Newbie

      I have operated under the principle that in new applications with the Faclets view handler it is best to run with the xmlparser NONE because it is the most efficient. (I have also run into cases where the NEKO filter itself introduces a problem).

      However, there can be problems when RichFaces components themselves break if the xml is not cleaned up by a filter. The most recent example is http://jira.jboss.com/jira/browse/RF-3577.

      So the question is, what is best practice?
      Should one strive to make everything work with xmlparser NONE?
      Do the RichFaces develpers consider it a bug if a component by itself does not work under NONE?