myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3894) Make the duplicate client id check optional in development mode
Date Mon, 19 May 2014 15:55:39 GMT


Leonardo Uribe commented on MYFACES-3894:

That's weird. The algorithm in place has been widely tested and it is pretty stable. I can't
imagine a situation where this could happen. There is a param to disable duplicate id check
on production org.apache.myfaces.CHECK_ID_PRODUCTION_MODE , but in development mode it is
always checked, by obvious reasons. Maybe is something related to the interaction in development.
If you make some changes in a page and the same component tree is used with a new fixed facelet,
a duplicate is possible, but the problem is not from MyFaces, because from start MyFaces don't
have the control, or the code cannot see this situation. It will never happen in production,
because in that moment the facelet files are static. We need more information about the steps
to reproduce the problem, to see if it is possible a workaround or something. Maybe set javax.faces.FACELETS_REFRESH_PERIOD=0
could help, because that setting force to compile the facelet every time, and that algorithm
is designed to discard the components related to a facelet that changed.

> Make the duplicate client id check optional in development mode
> ---------------------------------------------------------------
>                 Key: MYFACES-3894
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Wish
>            Reporter: Adam Balazs
>            Priority: Minor
> Hi, 
> I just wanted to start using JRebel with JSF, and found out that there are some issues
with the JRebel - MyFaces - PrimeFaces combo.
> It seems that some of the PF components generates invalid component trees,  which cause
the MyFaces throwing DuplicateIdException in development mode. The strange thing is that we
are using these components in production for more than 2 years now, and never noticed any
issues with them, so I guess, the guys at PF worked this around very well.
> I've already reported this to them with my company's PRO account.
> As I browsed the code of PF I realized that fixing this behavior is not so easy and can
take more time, so I just wonder if - as a quick fix - you can make the duplicate id check
algorithm optional in development mode too.

This message was sent by Atlassian JIRA

View raw message