File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JSF and the fly likes ajax4jsf-filter force-parser attribute not working Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » JSF
Bookmark "ajax4jsf-filter force-parser attribute not working" Watch "ajax4jsf-filter force-parser attribute not working" New topic

ajax4jsf-filter force-parser attribute not working

Nik Raut

Joined: May 23, 2005
Posts: 22

We're experiencing a performance issue with Ajax4JSF with respect to its Tidy plugin. We've dome some profiling and we've found the class/method: org.ajax4jsf.webapp.FilterServletResponseWrapper.parseContent is the biggest performance hog in the use case, consuming 90% of the process. I've tried to disable the tidy parser using components.xml by doing the following:

<web:ajax4jsf-filter force-parser="false" />

However, when we re-run the same tests, the profiling results are exactly the same each time. perhaps my understanding of this attribute is incorrect, but my hope was that it would not parse the entire page? If this is in correct, if we want to use the Neko parser, do we have to define it in web.xml?

In addition to trying to suppress this filter, we also tried NEKO plugin for filter but it broke most of the RichFaces component. We added the filters in web.xml as following:

Idea was to parse xyz.xhtml under abc folder to be parsed using NEKO and rest of the xhtmls using TIDY. Any idea what we might be doing wrong? Thanks.

To be yourself is the best thing to be.
Nik Raut

Joined: May 23, 2005
Posts: 22

I am still looking for possible solutions. Any help is welcome. Thanks.
I agree. Here's the link:
subject: ajax4jsf-filter force-parser attribute not working
It's not a secret anymore!