[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618428#comment-12618428
]
Jay Balunas commented on RF-10940:
----------------------------------
Thanks for the updated information, it will be very helpful in find the exact
point of the project. I think this is an important issue and we certainly want
to get it resolved!
Given the timing for 4.1.0.M1 ( code freeze this Friday ) I don't see us
getting this in. However we plan on addressing this and many other bugs in
M2/CR1, as M1 focused on new components. We are on monthly release cadence you
should see something soon.
In the mean time any more information or updates related to this?
> Client side validation refers to non existing javascript function
> -----------------------------------------------------------------
>
> Key: RF-10940
> URL: https://issues.jboss.org/browse/RF-10940
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.0.0.Final
> Reporter: Niels Soeffers
> Assignee: Jay Balunas
> Priority: Critical
> Labels: tran
> Fix For: 4.1.0.Milestone2
>
>
> Client Side Javascript functions are called on the component tags (for
> example onChange attribute) and defined at the bottom of the rendered page.
> We encountered a case where the function called in the onchange attribute is
> not defined at the bottom of the page.
> Our domain layer contains two different classes RG and SRG (they do not
> inherit from each other). However they both embed an embeddable class E with
> a field "name"
> In the GUI we have a page with a single form and two regions. One for adding
> a RG object and one for adding a SRG object. Both regions contain a
> h:inputText for the "name" field. So the first inputText is bound to
> {{RG.embedded.name}} and the second on {{SRG.embedded.name}}. Both inputTexts
> have a rich:validator tag as a child component.
> When the page is initially rendered both h:inputText have the same javascript
> function referred to in their onchange attribute (RGName_3Av).
> Which is not wrong because the validation (@NotNull on the "name" field in
> the Embedded class) is the same for both value bindings. It is a little bit
> confusing to see a method with a name of RGName_3Av on a component that is
> actually bound to SRG and so we would expect the method to call SRGName_3Av,
> but it's certainly not wrong and I even find it a very nice optimization.
> However when we click on an a:commandButton in the second region and rerender
> this second region, then suddenly the javascript function in the onchange
> attribute of the second inputText is changed and the name refers to the SRG
> component (SRGName_3Av), but this javascript method is never defined, because
> it was optimized when we initially rendered the complete page.
> Hope you can reproduce the problem with the above description and fix the
> problem or provide a workaround?
> Kind Regards,
> Niels
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
