Its the same problem as inputSuggestAjax. Chris Barlow and I wrote a patch for it but we haven't committed it yet. I'll try to get to it later today or tomorrow ...
sean On 11/2/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > @Sean - isn't that the same problem as with inputSuggestAjax? We > really should be able to find a component, even if it has forceId set > to true. > > There should be something like a central hashmap for all forceId'd > components. We can also do a duplicate check then. > > regards, > > Martin > > On 11/2/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > forceId only affects the clientId not the component id. > > > > sean > > > > On 10/28/05, Travis Reeder <[EMAIL PROTECTED]> wrote: > > > I tried this without setting the id, works fine. > > > I set the id, works fine. > > > Added forceId="true" and it cannot find it. > > > > > > Even though when I print out the component tree, the component id is > > > the same as the id I pass to findComponent: > > > > > > Here is the component output: > > > > > > <org.apache.myfaces.custom.inputAjax.HtmlSelectManyCheckboxAjax > > > id="smcb" FORMER_CHILD_IDS="[_id3]" forceIdIndex="true" forceId="true" > > > ... trimmed for space> > > > > > > And the id I'm using is in this log statement between the brackets. > > > > > > SEVERE: Component with id [smcb] not found in view tree. > > > > > > Anyone know offhand where the bug may lie? > > > > > > Travis > > > > > > > > -- > > http://www.irian.at > Your JSF powerhouse - > JSF Trainings in English and German >
