I'm not sure, but I would guess the reason for this is that if you create a component with an Id, that component binds to a specific markup. And if it is allowed to change it's id, it means that you could re-bind it with another (probably invalid) markkup, creating conflicts.
On Fri, Apr 11, 2008 at 5:18 PM, Korbinian Bachl - privat < [EMAIL PROTECTED]> wrote: > Hi, > > short question: Why isn't it possible to have a setId(String id) on the > components? - Is it really necessary that they know their id at > creation-time? > > Regards, > > Korbinian > -- Bruno Borges blog.brunoborges.com.br +55 1185657739 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld
