myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Andraschko (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (MYFACES-3894) Make the duplicate client id check optional in development mode
Date Mon, 19 May 2014 20:27:38 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002333#comment-14002333
] 

Thomas Andraschko commented on MYFACES-3894:
--------------------------------------------

Could you please create a issue on PrimeFaces side? I'm a PrimeFaces developer and MyFaces
User and i'm not aware of such a problem.
Maybe if you use the old 3.5 MenuModel stuff but this is outdated.

> Make the duplicate client id check optional in development mode
> ---------------------------------------------------------------
>
>                 Key: MYFACES-3894
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3894
>             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
(v6.2#6252)

Mime
View raw message