a reall UUID? that cant be then all the keys would change constantly... The point is that the paths of components on a page class are quite stable and for those the keys are stored If we use UUID for those then every key would be different for the "same" component on a page class
The thing is that it must be stable for a page.component... (and re occuring) johan On Mon, May 12, 2008 at 2:22 PM, Jan Kriesten <[EMAIL PROTECTED]> wrote: > > hi johan, > > and that would walk over the hierarchy.. how would that help? > > > > no, not walk the hierarchy, that wouldn't be that better (but at least it > wouldn't be recompiled every access). > > but you could just use a static getNextUid like you do at other places as > well (and that could be used as a stable id for repeaters as well btw). > > also getInputName is a bit smarter. That can stop with the first form it > > finds. Because an input name only have to be unique for the form. > > > > actually, on genereated forms this really get sick long ids as well which > doen't look nice in the html output at all. i can show you... ;-) > > best regards, --- jan. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
