Urgent Guidance Requested – Duplicate ID Issue

[paulbotta]

I am requesting guidance in troubleshooting an issue that is compromising an important deliverable. I have spent two days troubleshooting the issue and lack the expertise in understanding how to resolve it.

I am frequently receiving the following error:

javax.servlet.ServletException: duplicate Id for a component mainPane:dtlExpFrm:j_id220

The error will sometimes disappear when I stop Tomcat, clear the server cache and restart. I make no changes to the code, it is hit or miss.

Alternatively, I have gone through the pages and added IDs to all components identified in the affected form. I believe I have given each component an explicit ID.

If anyone can give me guidance on how I can resolve this issue, it would be greatly appreciated. Are there any tools that would help, or a specific set of steps to isolate it or any other way to identify the offending component?

I am using:

richfaces 3.3.1 GA
springframework 3.0
tomcat 6.0
ie 8
ff 3.5.3

[liuliu]

maybe un status

[ilya_shaikovsky]

seems that you have session scoped bindings.

[paulbotta]

liuliu - Sorry, I don't know what you mean by un status. Can you tell me more?

[paulbotta]

Ilya - After reading your response, I changed the bean scope to 'request' and restarted tomcat. I did not get the error, however, the page no longer functions as intended.

Are there any other work arounds, or is there a reference that you can point me to that would educate me in making a better design choice?

Thanks.

[juangon]

There are a definitive solution for this: CLIENT state saving.

Only you have to do is changing a context-param from web.xml:

<context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>client</param-value>
</context-param>

Perhaps after this you could see some errors during testing (like not serializable classes etc), but itsn't usual.

This option has the great advantage of saving all the view state in client (in one hidden form field with name "javax.faces.ViewState" or something like that), better IMHO than saving it in session (javax.faces.STATE_SAVING_METHOD=server).

To solve the problems of the beans to keep their state between requests, we have several beans in request scope with a4j:keepAlive. With that, the state of that beans "travel" along the client and server. Some disadvantage of this is the network traffic, increasing it because all of the data that have to be sent in every request.

Some info about this:
http://www.jroller.com/mert/entry/state_saving_method_client_side

[paulbotta]

juangon - Thank you very much for your input and the education. I made the modifications, but I am still seeing the same issue. I must be doing something else wrong, but I am at a loss at how to troubleshoot it.

[nbelaevski]

"paulbotta" wrote:
Ilya - After reading your response, I changed the bean scope to 'request' and restarted tomcat. I did not get the error, however, the page no longer functions as intended.

Are there any other work arounds, or is there a reference that you can point me to that would educate me in making a better design choice?

Thanks.

What do you need component bindings for?

[paulbotta]

Hi nvelaevski -

There is a page where the user enters customer information. They can edit one that they have selected, or press a button to add a new customer. What I have found was if the user enters data that fails validation, and then hits 'cancel'. The data that failed validation doesn't reset. I was binding to the rich:inplaceInput components so that I could explicitly reset the values under the above scenario.

[nbelaevski]

I see. This should work fine with request-scoped beans either.

[paulbotta]

I wanted to thank everyone who responded and got me in the right direction.

~Cheers