10:12 a.m.
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
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
6:50 a.m.
New subject: [JBoss JIRA] Assigned: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Nick Belaevski reassigned RF-10940:
-----------------------------------
Assignee: Pavel Yaschenko
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: Pavel Yaschenko
Labels: tran
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
6:50 a.m.
New subject: [JBoss JIRA] Updated: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Nick Belaevski updated RF-10940:
--------------------------------
Labels: tran (was: )
Pavel,
Please investigate this issue.
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: Pavel Yaschenko
Labels: tran
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
6:52 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas commented on RF-10940:
----------------------------------
This may be a duplicate issue, as I believe we've talked about this issue before.
Pavel/Alex please investigate and link/comment on 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: Pavel Yaschenko
Labels: tran
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
7:06 a.m.
New subject: [JBoss JIRA] Updated: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-10940:
-----------------------------
Priority: Critical (was: Major)
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: Pavel Yaschenko
Priority: Critical
Labels: tran
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
8:56 a.m.
New subject: [JBoss JIRA] Updated: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Pavel Yaschenko updated RF-10940:
---------------------------------
Fix Version/s: 4.1.0.Milestone1
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
8:58 a.m.
New subject: [JBoss JIRA] Resolved: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Pavel Yaschenko resolved RF-10940.
----------------------------------
Resolution: Done
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
9 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Pavel Yaschenko commented on RF-10940:
--------------------------------------
Client-side validation function is fixed, JSFunctionDefinition is refactored.
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
1:19 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Niels Soeffers commented on RF-10940:
-------------------------------------
Thanks for fixing this bug so quickly!
Is there a way I can download a nightly build somewhere with this fix already included?
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
10:29 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Pavel Yaschenko commented on RF-10940:
--------------------------------------
RichFaces 4 Nightly builds are currently not available, check
https://issues.jboss.org/browse/RFPL-1083. But you can get latest jars from
RichFaces Showcase 4.x SNAPSHOTS, check
http://www.jboss.org/richfaces/download/nightly page
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
2:28 a.m.
New subject: [JBoss JIRA] Reopened: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Niels Soeffers reopened RF-10940:
---------------------------------
Hello,
I originally logged this ticket, and was very happy when you guys solved the issue so
quickly. Since then we used the 4.1.0.SNAPSHOT jars for our project. And everything seemed
to work nicely. However last night a newly SNAPSHOT came in and our Selenium tests started
to fail. After some investigation on our side, it seems as this bug is reintroduced
again.
Kind Regards,
Niels
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
1:14 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Niels Soeffers commented on RF-10940:
-------------------------------------
Apparently it is not the exact same issue, however I do think we discovered a very related
one.
Don't know if I have to log a new issue for this, or reopen the original one?
When logging the original bug we only made use of the rich:validator. And that rich
validator was responsible for creating a javascript function. Which is still okay in the
nightly build. My apologies for my previous comment on that. What we discovered now is
that when we leave the rich:validator but we remove the @NotNull from the class, and
replace the @NotNull by a required="true" attribute on the rich:inputField then
the "required" attribute is going to do an ajax call in the function
(groupName_3av). However here we see the same problem appearing as we did before with the
client side validation. That is everything is going well as long as we don't rerender
the form. When we rerender the form the function is renamed as with the client side
validation but is not defined.
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: Pavel Yaschenko
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
12:16 p.m.
New subject: [JBoss JIRA] Assigned: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas reassigned RF-10940:
--------------------------------
Assignee: (was: Pavel Yaschenko)
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
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
10:55 a.m.
New subject: [JBoss JIRA] Assigned: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč reassigned RF-10940:
-------------------------------
Assignee: Lukáš Fryč
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: Lukáš Fryč
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
3:49 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Mano Swerts commented on RF-10940:
----------------------------------
Any news on this issue?
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: Lukáš Fryč
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
5:15 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Mano Swerts commented on RF-10940:
----------------------------------
Hi all,
Like my colleague stated in his last comment, this issue seems to be fixed only for
validations not using an ajax request. When the generated validation function uses an ajax
request to validate, the issue remains.
My colleague noted that setting the "required" attribute to "true"
uses ajax validation, so we worked around the problem by using @NotNull instead. However,
when working with java.util.Date objects on the backing bean, ajax validation is always
used. Also when using @NotNull. Because we cannot work around this issue with Date
objects, this issue is starting to be blocking for us. This issue raises JavaScript
errors, prevents our validation to be executed correctly and it even prevents
rich:calendar components to close automatically when selecting a date (due to the
JavaScript error).
We already use the 4.1-SNAPSHOT builds in our code due to several bugfixes in those
builds, so we are hoping that the fix for this issue will make it's way to the trunk
of 4.1 soon. Here is an example XHTML page and bean implementation for producing the
issue:
{code}
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a="http://richfaces.org/a4j"
xmlns:sec="http://www.springframework.org/security/facelets/tags"
xmlns:rich="http://richfaces.org/rich">
<f:view>
<h:head>
<title>Calendar Validation Test</title>
</h:head>
<h:body>
<h:form>
<h:outputLabel value="Start date" for="#{startDate}" />
<rich:calendar id="startDate"
value="#{calendarTestBean.startDate}">
<rich:validator />
</rich:calendar>
<h:outputLabel value="End date" for="#{endDate}" />
<a:outputPanel id="endDatePanel">
<rich:calendar id="endDate"
value="#{calendarTestBean.endDate}">
<rich:validator />
</rich:calendar>
</a:outputPanel>
<a:commandButton value="Rerender end date"
render="endDatePanel" />
</h:form>
</h:body>
</f:view>
</html>
{code}
{code}
package be.idewe.riscpro.ui;
import java.util.Date;
import javax.validation.constraints.NotNull;
import org.springframework.context.annotation.Scope;
import org.springframework.stereotype.Controller;
@Controller
@Scope("request")
public class CalendarTestBean {
@NotNull
private Date startDate;
@NotNull
private Date endDate;
public Date getStartDate() {
return startDate;
}
public void setStartDate(Date startDate) {
this.startDate = startDate;
}
public Date getEndDate() {
return endDate;
}
public void setEndDate(Date endDate) {
this.endDate = endDate;
}
}
{code}
The error message is as follows:
{code}
calendarTest.faces:5Uncaught ReferenceError: j_idt41_3AendDate_3Av is not defined
RichFaces.ui.Calendar.onchangecalendarTest.faces:5
$.extend.invokeEventrichfaces-base-component.js.faces:278
$.extend.setInputFieldcalendar.js.faces:1011
$.extend.__selectDatecalendar.js.faces:1633
$.extend.eventCellOnClickcalendar.js.faces:1084
(anonymous function)
{code}
Can we be kept up to date regarding the process? Thank you.
Kind regards,
Mano Swerts
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: Lukáš Fryč
Priority: Critical
Labels: tran
Fix For: 4.1.0.Milestone1
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
6:18 a.m.
New subject: [JBoss JIRA] Assigned: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas reassigned RF-10940:
--------------------------------
Assignee: Jay Balunas (was: Lukáš Fryč)
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.Milestone1
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
6:59 a.m.
New subject: [JBoss JIRA] Updated: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RF-10940:
-----------------------------
Assignee: (was: Jay Balunas)
Fix Version/s: 4.1.0.Milestone2
(was: 4.1.0.Milestone1)
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
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
6:59 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
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
7:48 a.m.
New subject: [JBoss JIRA] Assigned: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Jay Balunas reassigned RF-10940:
--------------------------------
Assignee: Brian Leathem
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: Brian Leathem
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
12:18 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-10940:
------------------------------------
I took a close look at this, and found that indeed the a4j framework is being smart about
not including duplicate javascript function definitions. The problem is that when the
part of the page is re-rendered, the reference to the original javascript method is lost.
As a workaround (which may not fit your use case), you can wrap all the ajax validation
components in an a4j:outputPanel, as in:
{code}
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a="http://richfaces.org/a4j"
xmlns:rich-in="http://richfaces.org/input"
xmlns:rich-v="http://richfaces.org/csv">
<f:view>
<h:head>
<title>Calendar Validation Test</title>
</h:head>
<h:body>
<h:form>
<h:outputLabel value="Start date" for="#{startDate}"
/>
<a:outputPanel id="datePanel">
<rich-in:calendar id="startDate"
value="#{calendarTestBean.startDate}">
<rich-v:validator />
</rich-in:calendar>
<h:outputLabel value="End date" for="#{endDate}"
/>
<rich-in:calendar id="endDate"
value="#{calendarTestBean.endDate}">
<rich-v:validator />
</rich-in:calendar>
</a:outputPanel>
<a:commandButton value="Rerender end date"
render="endDatePanel" />
</h:form>
</h:body>
</f:view>
</html>
{code}
This way, the components are aware of the shared javascript methods on each page
re-render.
To *actually* fix the problem, I believe we have to disable the logic that prevents
duplicate (logically) javascript functions from being defined. This seems like a
backwards step, so I'd like to investigate if it makes sense before proceeding.
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: Brian Leathem
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
12:59 a.m.
New subject: [JBoss JIRA] Commented: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-10940:
------------------------------------
Link to the discussion on the solution to this problem:
http://community.jboss.org/thread/171420
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: Brian Leathem
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
2:06 p.m.
New subject: [JBoss JIRA] Resolved: (RF-10940) Client side validation refers to non existing javascript function
[
https://issues.jboss.org/browse/RF-10940?page=com.atlassian.jira.plugin.s...
]
Brian Leathem resolved RF-10940.
--------------------------------
Resolution: Done
Changed getValidJavascriptName to use the MD5 hash of the script, rather than the
clientId
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: Brian Leathem
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
4848
days inactive
4976
days old
richfaces-issues@lists.jboss.org
22 comments
7 participants
participants (7)
-
Brian Leathem (JIRA) -
Jay Balunas (JIRA)
-
Lukáš Fryč (JIRA)
-
Mano Swerts (JIRA)
-
Nick Belaevski (JIRA)
-
Niels Soeffers (JIRA)
-
Pavel Yaschenko (JIRA)