myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott O'Bryan" <>
Subject Re: AJAX?
Date Wed, 24 Sep 2008 13:39:49 GMT
Ajax4JSF and Trinidad are indeed not compatible.  I think some people 
have hacked some stuff together, but many of these frameworks compete 
with each other for the AJAX request and I can't really see that 
changing until possibly JSF 2.0.

RichFaces is built on top of A4J toolkit which is why it is compatible.

I guess I don't understand what you mean by fine-grained Ajax things.  
Do you mean the ability to wrap non-ajax components into an AJAX 
response?  Because other then that I would put Trinidad's AJAX offering 
up against any of the other renderkits on flexibility and ease of use.


Jan-Kees van Andel wrote:
> Matthias,
> Just curiosity. The last time I've used Trinidad, it didn't really contain
> any ways to do some fine grained Ajax things. Integration with Ajax4jsf
> (that did offer low level Ajax) was also not implemented by both Ajax4jsf
> and Trinidad. That was basically my reason to stop with Trinidad and switch
> to RichFaces.
> Can you tell me something about the current status?
> Thanks,
> Jan-Kees
> Matthias Wessendorf-4 wrote:
>> On Sat, Sep 20, 2008 at 4:23 PM, Richard Yee <>
>> wrote:
>>> All of the trinidad components support what you want to to with ppr. All
>>> you
>>> need to do is add the partialTriggers="component Id" attribute to the
>>> component you want to update. On the select component, you would use the
>>> autosubmit and valueChangeListener attrs.
>> I'd also use Trinidad. It also offers a clean JS api, if you have some
>> use-cases beyond normal PPR.
>> Trinidad is basically framework and component lib.
>> -Matthias

View raw message