There are also changes in the 1.2 spec which may make forceId (partially) obsolete. Last I looked though it did not cover everything.
Interesting idea though about setting it on the components. sean On 10/21/05, Travis Reeder <[EMAIL PROTECTED]> wrote: > That'll work, but that's probably not the right way to do because if the > implementation changes then this won't work. Seems to me that there should > be a setForceId method on components. > > Travis > > > > > On 10/21/05, Volker Weber > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > to set forceId do dynamicaly created components you can do > > > > component.getAttributes().put(JSFAttr.FORCE_ID_ATTR, Boolean.True); > > > > this is what the tag does. > > > > Mike Kienenberger wrote: > > > That'd also mean that you couldn't use forceID from an alternate > > > ViewHandler facelets or Shale/Clay as well since the *Tag isn't used. > > > > > > On 10/21/05, Travis Reeder <[EMAIL PROTECTED]> wrote: > > > > > >>Any reason for this? Why I ask is because when creating components > > >>programatically, you can't setForceId(). > > >> > > >> Travis > > >> > > >> > > > > > > > > > > -- > > Don't answer to From: address! > > Mail to this account are droped if not recieved via mailinglist. > > To contact me direct create the mail address by > > concatenating my forename to my senders domain. > > > >
