can you post your JSP? regards,
Martin On 12/24/05, Mike Duffy <[EMAIL PROTECTED]> wrote: > Simon, > > Thx for the detailed response. > > You stated: "Just to be clear: this warning is only generated when a > component is created *by java > code* and added to the tree. In this case, the id must be explicitly set by > the code." > > I am not adding any components through code. > > I am getting this error when using t:dataTable with t:dataScroller. Perhaps > there is a bug in > this code caused by not setting the ID correcty? > > Mike > > > --- Simon Kitching <[EMAIL PROTECTED]> wrote: > > > Hi Mike, > > > > Maybe you can't see anything in the HTML because the component has > > "rendered=false"? You can try turning up the logging configuration; the > > entire component tree is logged at DEBUG level under category > > org.apache.myfaces.util.DebugUtils > > > > Just to be clear: this warning is only generated when a component is > > created *by java code* and added to the tree. In this case, the id must > > be explicitly set by the code. > > > > On the first render of a JSP page, as JSF *tags* are encountered, the > > corresponding components are created and assigned ids generated using an > > incrementing counter. > > > > On a re-render of the page, as JSF tags are encountered the tag needs to > > find the correct *existing* JSF component object and attach to it. For > > components that have explicit ids in the page, that's easy. For > > components that have auto-generated ids, this process depends upon the > > id values being generated in exactly the same sequence as the original > > visit to the page. > > > > But if user code adds a component with NO id to the page, then the > > unique counter must be used to allocate an id for that component, and > > that can stuff up the rematching stuff on later re-renders, causing JSF > > tags to connect to the wrong components. That's not good, hence the > > warning message. > > > > Perhaps this could be fixed by allocating ids for manually-added > > anonymous components using a different prefix and counter? eg using > > _code3 rather than _id3? Any such change would not be high priority > > though; user code really should just set the id on any components it > > creates. > > > > Cheers, > > > > Simon > > > > > > > > Mike Duffy wrote: > > > I meant to say, "when I do a view source on the JSP [and look at the > > > HTML] I can not find an > > > identifier for _id229. > > > > > > Seems odd. > > > > > > Mike > > > > > > > > > --- Martin Marinschek <[EMAIL PROTECTED]> wrote: > > > > > >> The warning is a bit odd in that it spits out the automatically > > >> generated id, which you won't see in the JSP source ;) > > >> > > >> You should be able to find it in the HTML source, though! > > >> > > >> regards, > > >> > > >> Martin > > >> > > >> On 12/23/05, Mike Duffy <[EMAIL PROTECTED]> wrote: > > >>> I see this warning, "WARNING: Component _id229 just got an automatic > > >>> id,", but when I do a > > >> view > > >>> source on the JSP I can not find an identifier for _id229. > > >>> > > >>> This seems odd. Anyone know why the id wouldn't be there? > > >>> > > >>> Thx. > > >>> > > > > > > > > > > > > > > > > __________________________________ > Yahoo! for Good - Make a difference this year. > http://brand.yahoo.com/cybergivingweek2005/ > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
