[
https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.s...
]
Michael B commented on RF-13595:
--------------------------------
And that's exactly what we tested: <a4j:ajax event="blur"
render="inputField" />
The workaround with a4j:ajax executes the validation (after the first JS error occurs) and
surely works in a simple example like the given test project, but produces other problems
in more complex page layouts with various components.
Also the workaround ist not applicable for other input components like rich:calendar etc.
where the component stops working.
You could replace the inputText in the test application by the rich:calendar component and
of course also change the input field/validator in the backing bean to a java.util.Date.
Effect is, that the validation fails when you select a date in the calendar pop-up and the
pop-up does not close due to the processing error in JS.
That's why I think that's a more general problem with JS loading that affects more
than what could be solved with the workaround - unfortunately...
rich:validator doesn't work when loaded via ajax (re-render)
------------------------------------------------------------
Key: RF-13595
URL:
https://issues.jboss.org/browse/RF-13595
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-validators
Affects Versions: 4.3.5
Environment: RF 4.3.5
Mojarra 2.1.27
Java 7 Update 51 x64
Tomcat 7.0.52
Firefox 28.0 + Firebug
Reporter: Michael B
Attachments: validationTest.zip
When loading input components with a rich:validator via ajax (re-render), client side
validation bridge breaks due to a missing JS function av_xxxxxxxxx.
As already described in further detail in a comment to this JIRA here:
https://issues.jboss.org/browse/RF-12031
I've created a very basic example project to reproduce the problem for a single input
field which becomes visible (re-rendered) when you click on an a4j:commandButton.
Please note that this is a minimum example only. The problem is also reproducable for
other input components besides h:inputText - like for example rich:calendar.
The workaround described in the referenced JIRA creates other problems in client JS when
combined with other components like rich:focus and is also not applicable for other input
components besides h:inputText.
We think the problem is located in the way JS functions are optimized for being re-used
as well as in the way they are (not) being added on the client side when a component
becomes visible on ajax response re-rendering.
Please use attached eclipse project to easily reproduce the problem => open Firefox
=> Firebug console to see the error about the missing JS function av_xxxxxxx ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira