Hi,
I had a similar problem of duplicate client id, but in a non-portlet
environment. My Tag handler for the component, as well as the component
itself has overriden the getClientId() method, such that they were returning
different id's. This was causing the JSPViewHandler (in the RENDER_RESPONSE
phase) to think that the component did not exist in the view_root. It went
ahead and created a second component which had the same client_id's as the
first one. Both were then rendered resulting in a "duplicate client id"
exception.
I am not sure if this is the cause of your problem. It might help to
investigate along these lines.
--
Regards
Parag
On 7/11/07, Marcelo Ohashi <[EMAIL PROTECTED]> wrote:
Hi,
Does anyone know how to prevent this error to happen? Maybe
somebody have a patch to apply?
It seems it is not checking if the component is already
registered. Is there a way to check and fix this error?
I'm running it on a Portlet Container on Sun Java Appliction
server 8.2.
Thanks in advance.
Marcelo Ohashi
