[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13317:
----------------------------
Fix Version/s: 5.0.0.Alpha3
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
> Key: RF-13317
> URL: https://issues.jboss.org/browse/RF-13317
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
> Reporter: Matti Bickel
> Assignee: Pavel Slegr
> Priority: Critical
> Labels: jsf22
> Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {quote}
--
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, 3 months
[JBoss JIRA] (RF-13062) r:validator stops working
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13062.
-----------------------------
Resolution: Cannot Reproduce Bug
> r:validator stops working
> -------------------------
>
> Key: RF-13062
> URL: https://issues.jboss.org/browse/RF-13062
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing.
--
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, 3 months
[JBoss JIRA] (RF-13062) r:validator stops working
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13062?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13062:
---------------------------------
[~jhuska] the provided sample works fine on WildFly 8.0.0.Beta2-SNAPSHOT (you can obtain binary e.g. here: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil... ), so I guess it will be fixed in 8.0.0.CR1. (Please check once 8.0.0.CR1 is available)
Additionally, I have reviewed the framework tests and all tests related to validation successfully pass.
> r:validator stops working
> -------------------------
>
> Key: RF-13062
> URL: https://issues.jboss.org/browse/RF-13062
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I just tried r:validator with the current snapshot for WildFly 8.0.0.Alpha2 (changed Mojarra 2.2.0 to 2.1.23). However, if I'm doing a wrong input nothing happens. No error message, no stacktrace, just nothing.
--
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, 3 months
[JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller
by Anton Bogoslavskyi (JIRA)
Anton Bogoslavskyi created RF-13427:
---------------------------------------
Summary: ED, Datatable: table needs to define the number of rows itself when using dataScroller
Key: RF-13427
URL: https://issues.jboss.org/browse/RF-13427
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.3.3
Reporter: Anton Bogoslavskyi
Attachments: data-3.png, datatable-1.png
I need using pagination for extendedDataTable control.
My row's height depends on the data it contains.
I need the table to be constant height, so I specify the height in css.
I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller.
So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears.
Both situations are not user friendly.
Actually on each page I need the maximum rows number to fit the height.
--
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, 3 months
[JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller
by Anton Bogoslavskyi (JIRA)
[ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.s... ]
Anton Bogoslavskyi updated RF-13427:
------------------------------------
Attachment: datatable-1.png
data-3.png
> ED, Datatable: table needs to define the number of rows itself when using dataScroller
> --------------------------------------------------------------------------------------
>
> Key: RF-13427
> URL: https://issues.jboss.org/browse/RF-13427
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Reporter: Anton Bogoslavskyi
> Attachments: data-3.png, datatable-1.png
>
>
> I need using pagination for extendedDataTable control.
> My row's height depends on the data it contains.
> I need the table to be constant height, so I specify the height in css.
> I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller.
> So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears.
> Both situations are not user friendly.
> Actually on each page I need the maximum rows number to fit the height.
--
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, 3 months
[JBoss JIRA] (RF-13392) TreeSelectionChangeEvent always triggered during Apply Request Phase
by Andreas Hahne (JIRA)
[ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.s... ]
Andreas Hahne updated RF-13392:
-------------------------------
Workaround Description: In this situation, setting the attribute {{execute}} for {{rich:tree}} to {{@this}} and specifing the {{rich:panel}}'s ID in the {{render}} attribute solved the problem.
> TreeSelectionChangeEvent always triggered during Apply Request Phase
> --------------------------------------------------------------------
>
> Key: RF-13392
> URL: https://issues.jboss.org/browse/RF-13392
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tree
> Affects Versions: 4.3.3
> Reporter: Andreas Hahne
> Labels: richfaces, selectionChangeListener, tree
> Fix For: 5-Tracking
>
> Attachments: tree.zip
>
>
> When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false.
> This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely.
--
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, 3 months
[JBoss JIRA] (RF-13426) Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13426?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13426:
-------------------------------
Fix Version/s: 4.5.0.Alpha2
> Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1
> ----------------------------------------------------------------------------
>
> Key: RF-13426
> URL: https://issues.jboss.org/browse/RF-13426
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 4.5.0.Alpha2
>
>
> In showcase footer page section, there is _RichFaces Framework by JBoss by Red Hat, version 5.0.0.Alpha2_.
> It should be with 4.5.0.Alpha1.
> The version is so because it is retrieved from {{VersionBean}}, which is from the 5.0.0.Alpha2 framework.
> IMHO it can cause some misunderstanding, or do we want to stress that the core is from RF 5 ?
--
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, 4 months