[JBoss JIRA] (RF-13185) Quickstarts: Modify GAV to use org.jboss.quickstarts.rf
by Sande Gilda (JIRA)
Sande Gilda created RF-13185:
--------------------------------
Summary: Quickstarts: Modify GAV to use org.jboss.quickstarts.rf
Key: RF-13185
URL: https://issues.jboss.org/browse/RF-13185
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: examples
Reporter: Sande Gilda
As part of the BOM, Stacks, Archetypes, and Quickstarts reorganization process, we are standardizing on the quickstarts GAV to use 'org.jboss.quickstarts.<product-name>.
Could you change the RichFaces quickstarts GAV from 'org.jboss.as.quickstarts' to 'org.jboss.quickstarts.rf'?
This can be done at a time that works best with your release schedule.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek edited comment on RF-13127 at 9/10/13 9:04 AM:
-----------------------------------------------------------
I can confirm, that rich:validator behaves incorrectly, when placed in iteration component, validates a String value and uses onvalid/oninvalid functions with parameters.
It seems that the parameters for these function are not forwarded correctly when using some string validations.
I've attached another sample (RF-13127.zip), using rich:repeat instead of dataTable, and only with one set of string validated and one set of number validated inputs.
In this sample, all string validated inputs (vin) forwards the same parameters (id of first vin input) to the onvalid/oninvalid function.
was (Author: jstefek):
I can confirm, that rich:validator behaves incorrectly, when placed in iteration component, validates a String value and uses onvalid/oninvalid functions with parameters.
It seems that the parameters for these function are not forwarded correctly when using some string validations.
I've attached another sample, using rich:repeat instead of dataTable, and only with one set of string validated and one set of number validated inputs.
In this sample, all string validated inputs (vin) forwards the same parameters (id of first vin input) to the onvalid/oninvalid function.
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Assignee: Jiří Štefek
> Attachments: JSFTemplate.zip, RF-13127.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek reassigned RF-13127:
--------------------------------
Assignee: (was: Jiří Štefek)
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Attachments: JSFTemplate.zip, RF-13127.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-13127:
-----------------------------
Steps to Reproduce:
# unzip RF-13127.zip and open the folder
# run mvn jetty:run
# open http://localhost:8080/richfaces/home.faces
# change e.g. the third vin input to 'a'
** expected: the third vin input is changed by the user function
** have: the first vin input is changed by the user function
# change e.g. the third mileage input to 'a'
** works correctly
I can confirm, that rich:validator behaves incorrectly, when placed in iteration component, validates a String value and uses onvalid/oninvalid functions with parameters.
It seems that the parameters for these function are not forwarded correctly when using some string validations.
I've attached another sample, using rich:repeat instead of dataTable, and only with one set of string validated and one set of number validated inputs.
In this sample, all string validated inputs (vin) forwards the same parameters (id of first vin input) to the onvalid/oninvalid function.
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Assignee: Jiří Štefek
> Attachments: JSFTemplate.zip, RF-13127.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13183) Autocomplete: behavior of component with tokens changed
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13183:
----------------------------------
Summary: Autocomplete: behavior of component with tokens changed
Key: RF-13183
URL: https://issues.jboss.org/browse/RF-13183
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, regression
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
JBoss AS 7.2.0.Final-redhat-8
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 29.0.1547.65 @ Linux x86_64
Reporter: Pavol Pitonak
# (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved)
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
# type "a" into input
# select Alabama
result:
* output contains "Alabama," but should be "Alabama"
* it would output "Alabama" in 5.0.0.Alpha1
* this behavior is influenced by "tokens" attribute
--
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
10 years, 9 months
[JBoss JIRA] (RF-13182) Autocomplete: attributes style and styleClass missing
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13182:
----------------------------------
Summary: Autocomplete: attributes style and styleClass missing
Key: RF-13182
URL: https://issues.jboss.org/browse/RF-13182
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, regression
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
JBoss AS 7.2.0.Final-redhat-8
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 29.0.1547.65 @ Linux x86_64
Reporter: Pavol Pitonak
Component autocomplete is missing two attributes - style and styleClass. There attributes were present in 5.0.0.Alpha1.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13181) Autocomplete: suggestion list is not valid HTML code
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13181:
----------------------------------
Summary: Autocomplete: suggestion list is not valid HTML code
Key: RF-13181
URL: https://issues.jboss.org/browse/RF-13181
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
JBoss AS 7.2.0.Final-redhat-8
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 29.0.1547.65 @ Linux x86_64
Reporter: Pavol Pitonak
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
# type "a" into input
# check suggestion list's markup
result:
* Autocomplete generates an unsorted list (ul) with several list items (li), one for each suggestion. However, inside each li, there is yet another li which is not allowed by HTML.
{code:xml}
<ul class="ui-autocomplete ui-menu ui-widget ui-widget-content ui-corner-all" id="ui-id-1" tabindex="0" style="z-index: 1; display: block; top: 237.0142364501953px; left: 10px; width: 161px;">
<li class="ui-menu-item" role="presentation">
<a id="ui-id-7" class="ui-corner-all" tabindex="-1">
<li>Alabama</li>
</a>
</li>
...
</ul>
{code}
--
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
10 years, 9 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-13127:
-----------------------------
Attachment: RF-13127.zip
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Assignee: Jiří Štefek
> Attachments: JSFTemplate.zip, RF-13127.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
10 years, 9 months
[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13180:
----------------------------------
Summary: Autocomplete: ajax doesn't work with change event
Key: RF-13180
URL: https://issues.jboss.org/browse/RF-13180
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, regression
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
JBoss AS 7.2.0.Final-redhat-8
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 29.0.1547.65 @ Linux x86_64
Reporter: Pavol Pitonak
Priority: Blocker
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
# type "a" into input
# select Alabama
result:
* ajax request is not fired
* output is not updated
* when "change" event in r:ajax is changed to "blur", the use-case works
--
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
10 years, 9 months