Hi! Not sure if this really helps. Both teams do a awesome job with getting their component libs to JSF-2. But as with Trinidad, Primefaces also still uses a proprietary way to do partial page rendering (<p:ajax>). A JSF-2 component lib should at least be working if <f:ajax> is used in a page too. Then it's most likely that you can really mix and match different components of multiple libs.
LieGrue, strub --- On Thu, 7/15/10, Cagatay Civici <[email protected]> wrote: > From: Cagatay Civici <[email protected]> > Subject: Re: [Trinidad] need timelines for the Trinidad 2 release > To: "MyFaces Discussion" <[email protected]> > Date: Thursday, July 15, 2010, 8:49 AM > Hi Venkat, > > You can use PrimeFaces with Trinidad. > > http://cagataycivici.wordpress.com/2010/03/24/integrating-primefaces-and-apache-trinidad/ > > Even the Trinidad's casablanca skin together; > > http://cagataycivici.wordpress.com/2010/06/24/apache-trinidads-casablanca-skin-as-a-primefaces-theme/ > > Cagatay > > On Jul 15, 2010, at 6:07 AM, Venkat Ramanan Viswanathan > wrote: > > > HI > > > > Can some one share the timelines for Trinidad 2 final > release. We are still > > using alpha 2 for our environment and it is quite > stable except that > > <f:ajax> is not working correctly. Can some one > share the dates for RC1, RC2 > > and final production release. > > > > Also are there plans to make it work with other > frameworks ? Currently if we > > use trinidad components, we cannot mix them with other > jsf component > > frameworks like richfaces , primefaces , > Icefaces as the PPR concepts are > > different in each framework. > > > > Thanks > > Venkat > >
