I was referencing what Manfred said (don't want to steal your idea). What I meant was that if we use the same name for an extended component as one that's in the standard set (x:datatable -> h:datatable), the extended component should behave in exactly the same manner as its corresponding standard component if the same attribute values are passed through.
In this specific case, the preserveDataModel should be false since that would lead to behavior just like the <h:datatable />. If there becomes a case where we cannot provide exactly the same functionality with the same attribute values, we should rename the extended component. On Mon, 21 Mar 2005 09:34:42 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > Yes I agree with Heath's statement as well (that extended components > should have the same defaults as the standard components.) I just > didn't understand how that statement was related to x:dataTable > because the preserveDataModel attribute only applies to MyFaces. > > I agree it should default to false since its not something a new user > would expect to have. I assume that is what Heath meant. > > sean > > > On Mon, 21 Mar 2005 10:22:21 -0400, Sylvain Vieujot <[EMAIL PROTECTED]> wrote: > > I agree with Heath. > > > > Yes, preserveDataModel is MyFaces specific, that's why it should default to > > false. > > > > > > On Mon, 2005-03-21 at 09:13 -0500, Sean Schofield wrote: > > > I think as a more general rule, it would be best if the extended > > > components set behaved exactly like the regular component set by > default. > > This would ease entry into the component set for other > developers. But > > isn't preserveDataModel MyFaces specific? > -Heath Borders-Wing sean > -- -Heath Borders-Wing [EMAIL PROTECTED]
