Duplicate Id with rich:extendedDataTable

[evialxg]

Hello

I am getting this rather familiar to many of you error :

         java.lang.IllegalStateException: duplicate Id for a component queryPageBottomForm:j_id44

           ..............

          ...............

I am using a rich:extendedDataTable control whose columns and content i am creating on my own, i.e I create the components programmatically.

I have been very careful in defining my own ids for the components (static or dynamic ones).

The above error comes up on sorting and filtering (i use the default sorting and filtering utilities of the table for this purpose)  and navigation to another page (i use the rich:datascroller component ) after some of the entries on the table have changed. e.g after deleting an entry, the sorting gives me this error.  Can you mention any other factor other than omitting ids that can cause this problem?  The page containing the table is included in a parent page  like this :

     <jsp:include page="queryPageBottomJSF.jsp" flush="true">
    </jsp:include>

  and it contains the table in this way:

    <h:form binding="#{queryPageBottomJSF.queryPageBottomForm}" id="queryPageBottomForm" > 
       .....

         <rich:extendedDataTable> ...</rich:extendedDataTable>
     

  </h:form>

The  "queryPageBottomJSF" is a reference to a request scope bean.

Any idea would be appreciated.  Thanx!

[eugenbesel]

what will happen, when you use sessionScope??

[evialxg]

nothing changes.. but it's no good using session scope beans in such a case.

[liuliu]

hi,

i got this kind of error sometimes when jsf cant creat his view. it throws this exception for first componnent in the page included.

hope this helps

liu

[ilya_shaikovsky]

duplicates Id's is most common problem which occurs while using session scoped component bindings. And it's not related to RichFaces but just pure JSF restriction.

[ilya_shaikovsky]

I get the point that in your case bean is request scoped. just looked to the post where session was suggested. Try to assighn id's explicitly to all the component you adding to tree.

[evialxg]

Thanks for the suggestion. Ids are already checked. In this case, there  is probably a component that i am unable to notice.

However, i 'd like to add that the exact same error comes up with ids that i have created on my own, which means that probably just defining your own ids and using request scope objects is not enough to get rid of this problem.!!

[ilya_shaikovsky]

do you able to provide simple war sample with java sources?

[evialxg]

I  finally overcame the problem by removing a jsp:include tag i used on the page and inserting the whole code of the included page directly.

So, it seems that the jsp:include tag creates some conflicts with the ids.