The purpose of this posting here is because the nesting of components ( say the below input field within a primefaces panel ) or the usage of event handlers such as p:ajax, could be influential to cause some of the issues. It was my intention to share and obtain other primefaces community user's experience on this issue, which is the purpose of this community forum as well. All users here are also interested to issues that are related to JSF. The combining aspect is that we are primefaces + JSF2 users and we all combine both technologies together.
Having said that... Back to the issue:
I have created a test case that has proven the issue to be JSF2 specific. I have created non primefaces pages where any field setter ( therefore not only HashMaps ) will never trigger if the property field is nested within a JSF container such as UIPanel ( h:panelGrid ) or other container and such container was generated through the binding attribute ( such as
Code: Select all
<h:panelGrid binding="#{myBinderBean.myPanelComponent}" /> )
.
A
bug report was created with Oracle (former Sun) to trach this issue. The bug report is under review and if screened positive I will post its reference here.