PrimeFaces Ajax API

[Oleg]

Hi Cagatay,

I would like to aks about JavaScript Ajax API. Do you have a documentation of using this "native" built-in API or is it a black box for us? Here is the standard for JSF 2 http://java.sun.com/javaee/javaserverfa ... .ajax.html. But what is about if we want to use PrimeFaces Ajax in JavaScript or write own components based on PrimeFaces one? I know you have two PhaseListener's which check PrimeFaces specific calls. This is another reason to use your API and not one from JSF 2 standard (although standard API should cause no problems).

Off topic: I've saw you use YUI Compressor Maven PlugIn. We use it too (compress and aggregation). This PlugIn was updated some time ago. The groupId were renamed and there is a new version 0.9. http://alchim.sourceforge.net/yuicompre ... index.html.

Best regards.
Oleg.

[cagatay.civici]

Hi Oleg,

I'm writing the updated version of User's Guide nowadays, I'll add a section about PrimeFaces ajax API with examples.

Regarding YUI compressor plugin, yes I use it to compress js and css PrimeFaces contains at build time. I'll look into the new version.

Thanks for the feedback

[Oleg]

Hello Cagatay,

Super, I'm curious about it. Thanks a lot for good news. Hopefully we can use PrimeFaces Ajax API in almost the same simple manner as standard API

By the way, did you already think about various Factory implementations creating custom PartialViewContext (for PrimeFaces Ajax), FacesConfig (for RequestContext encapsulation), ResourceHandler (for PrimeFaces resource loading) etc.? Maybe you can get rid of PhaseListeners. I don't really like PhaseListeners because they are performed for each request. That was just a question of course. Thanks.

- Oleg.

[cagatay.civici]

I agree that exposing PrimeFaces Ajax API can help implementors to come up with their own PrimeFaces powered components.

I don't think we can remove phaselisteners in JSF 1.2/PrimeFaces 1.x but maybe for JSF 2.0/PrimeFaces 2.x. PhaseListeners are executed in each request but it has almost no performance effect as it's at most two if statements to process. Considering what other libraries do to our applications with ViewHandlers, StateManagers, Servlet Filters, Html Parsers and more, I think PrimeFaces does a good job at having almost no effect on performance.