Re: Triniad ..

Thanks Manuel for writing this. We've had some shifting priorities and releases have been somewhat limited as of late. However, I raised this issue with my team and in response to your email and was able to secure a commitment to allowing me some time to do quarterly releases. Trinidad remai

Triniad ..

Hi MyFaces Trinidad2-Team, Is there anything happening for MyFaces Trinidad 2 in the (near, middle, any) future? If not, could you please officially bury Trinidad, so that i have more arguments for project lead/marketing, that we have to go away from this project risk? :) Regards, Manuel. -- D

Re: Triniad 2.0.1 release ?

The answer is yes. We've got a few blockers that are being worked on, hopefully we can get to them this week. Sent from my iPhone On Aug 29, 2011, at 4:22 AM, Manuel Hartl wrote: > Hi Trinidad-Team, > > is there going to be a Trinidad 2.0.1 release soon? We need some of the > fixes that were d

Triniad 2.0.1 release ?

Hi Trinidad-Team, is there going to be a Trinidad 2.0.1 release soon? We need some of the fixes that were done in the 2.0.1-SNAPSHOT version .. Regards, Manuel. -- Dipl. Inform. Manuel Hartl Software Architect FlexSecure-LogoKobilGroup-Logo FlexSecure GmbH Industriestr. 12 D - 64297 D

Re: [Trinidad] Triniad 1.2 not using component.encodeAll()

encodeAll is a convenience method for renderers to call on their children, it is not for component authors to extend necessarily. encodeAll is just a wrapper on the code that is necessary to call encodeBegin, encodeChildren and encodeEnd. As the spec says, it is the preferred, not required method,

[Trinidad] Triniad 1.2 not using component.encodeAll()

I just tried to create a very simple custom component. It worked exactly iff the parent component is not a Trinidad component. Turned out that overwriting encodeAll() has no effect in that case, since Trinidad's CoreRenderer does not use that method, but rather calls the individual encodeBegin()