[JBoss JIRA] (RF-13150) Remove JMS functionality from the RichFaces showcase
by Brian Leathem (JIRA)
Brian Leathem created RF-13150:
----------------------------------
Summary: Remove JMS functionality from the RichFaces showcase
Key: RF-13150
URL: https://issues.jboss.org/browse/RF-13150
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-push/poll, showcase
Reporter: Brian Leathem
Fix For: 4.3.4
The RichFaces showcase currently includes a demo of RichFaces push backed by JMS. The JMS security configuration however is not portable, and leads to difficulties in running the RichFaces showcase in other containers.
We target the showcase at demonstrating component capabilities, and leave the JMS integration to be demonstrated as a developer example. The caveat here is that we do a better job promoting the availability of our developer examples.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Description:
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 value="#{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
onvalid="valueModified(#{rich:element('myField')})"/>
</h:inputText>
{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.
was:
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 always returns the element from row zero 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 value="#{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
onvalid="valueModified(#{rich:element('myField')})"/>
</h:inputText>
{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.
> 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
> Labels: waiting_on_user
> Attachments: JSFTemplate.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 value="#{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
> onvalid="valueModified(#{rich:element('myField')})"/>
> </h:inputText>
> {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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Description:
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 always returns the element from row zero 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 value="#{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
onvalid="valueModified(#{rich:element('myField')})"/>
</h:inputText>
{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.
was:
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 always returns the element from row zero 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 value="#\{myBean.myField}" id="myField">
<rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
onvalid="valueModified(#\{rich:element('myField')})"/>
</h:inputText>
{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.
> 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
> Labels: waiting_on_user
> Attachments: JSFTemplate.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 always returns the element from row zero 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 value="#{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#{rich:element('myField')})"
> onvalid="valueModified(#{rich:element('myField')})"/>
> </h:inputText>
> {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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi commented on RF-13127:
-----------------------------------
I attached a project to demonstrate the issue. Unzip and run project with mvn jetty:run. Go to http://localhost:8080/webtemplate. Log in with credentials user/user. Go to the Table Edit page from the toolbar. Edit fields in rows after the first row. The string fields intermittently do not return the correct element. The BigDecimal fields seem to always return the correct element. I have an alert that displays which element was passed by the oninvalid and onvalid tags.
> 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
> Labels: waiting_on_user
> Attachments: JSFTemplate.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 always returns the element from row zero 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 value="#\{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
> onvalid="valueModified(#\{rich:element('myField')})"/>
> </h:inputText>
> {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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Attachment: JSFTemplate.zip
Attached JSF project
> 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
> Labels: waiting_on_user
> Attachments: JSFTemplate.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 always returns the element from row zero 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 value="#\{myBean.myField}" id="myField">
> <rich:validator oninvalid="valueModifiedAndError(#\{rich:element('myField')})"
> onvalid="valueModified(#\{rich:element('myField')})"/>
> </h:inputText>
> {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
12 years, 7 months
[JBoss JIRA] (RF-13133) ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13133?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13133:
------------------------------------
Verified, issue can be closed.
> ExtendedDataTable: filterType=custom doesn't work when mixing custom and built-in filter columns
> ------------------------------------------------------------------------------------------------
>
> Key: RF-13133
> URL: https://issues.jboss.org/browse/RF-13133
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.1
> Environment: Tomcat 7, Mojarra 2.1.21
> Reporter: dako ak
> Assignee: Brian Leathem
> Labels: testcase_provided
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> According to my appended test project:
> I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13149) a4j:push in Metamer doesn't have subtopic name
by Petr Mensik (JIRA)
Petr Mensik created RF-13149:
--------------------------------
Summary: a4j:push in Metamer doesn't have subtopic name
Key: RF-13149
URL: https://issues.jboss.org/browse/RF-13149
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.3
Environment: Fedora 18, JBoss EAP 6.1, Firefox 23
Reporter: Petr Mensik
If you try to send a message through Message Producer under a4j:push section, then the following exception is thrown
java.lang.IllegalArgumentException: Subtopic name '' does not match pattern ([a-zA-Z0-9_]+|#\{.+\})
--
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
12 years, 7 months