[JBoss JIRA] (RF-13293) accordion: JS API: bugs of function switchTo()
by Jiří Štefek (JIRA)
Jiří Štefek created RF-13293:
--------------------------------
Summary: accordion: JS API: bugs of function switchTo()
Key: RF-13293
URL: https://issues.jboss.org/browse/RF-13293
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 5.0.0.Alpha1, 4.3.4
Reporter: Jiří Štefek
Bug #1 -- @cycledSwitching
Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
E.g.:When you use function _switchTo(nextItem())_
* it switches to next item, but
** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
----
Bug #2 -- result of function _switchTo()_ can be used without params
Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null) it simply switches to next item.
The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem_ returns null).
--
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, 6 months
[JBoss JIRA] (RF-13293) accordion: JS API: bugs of function switchTo()
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13293?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-13293:
-----------------------------
Description:
Bug #1 -- @cycledSwitching
Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
E.g.:When you use function _switchTo(nextItem())_
* it switches to next item, but
** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
----
Bug #2 -- result of function _switchTo()_ can be used without params
Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null) it simply switches to next item.
The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem()_ returns null).
was:
Bug #1 -- @cycledSwitching
Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
E.g.:When you use function _switchTo(nextItem())_
* it switches to next item, but
** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
----
Bug #2 -- result of function _switchTo()_ can be used without params
Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null) it simply switches to next item.
The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem_ returns null).
> accordion: JS API: bugs of function switchTo()
> ----------------------------------------------
>
> Key: RF-13293
> URL: https://issues.jboss.org/browse/RF-13293
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.4, 5.0.0.Alpha1
> Reporter: Jiří Štefek
>
> Bug #1 -- @cycledSwitching
> Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
> E.g.:When you use function _switchTo(nextItem())_
> * it switches to next item, but
> ** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
> ** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
> ----
> Bug #2 -- result of function _switchTo()_ can be used without params
> Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null) it simply switches to next item.
> The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem()_ returns null).
--
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, 6 months
[JBoss JIRA] (RF-12008) Add RichFaces AS7/WildFly module to distribution
by Radim Hanus (JIRA)
[ https://issues.jboss.org/browse/RF-12008?page=com.atlassian.jira.plugin.s... ]
Radim Hanus commented on RF-12008:
----------------------------------
recently I ran into the problems trying to use both richfaces as module and rich:tree component along with org.richfaces.model.TreeNodeImpl
there is some classloading issue, following exception is raised:
org.richfaces.model.TreeNodeImpl cannot be cast to javax.swing.tree.TreeNode
actually I can't find a relevant forum thread where Nick Belaevski answers why
> Add RichFaces AS7/WildFly module to distribution
> ------------------------------------------------
>
> Key: RF-12008
> URL: https://issues.jboss.org/browse/RF-12008
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Lukáš Fryč
> Fix For: 5-Tracking
>
>
> It would be nice to have RichFaces packed as JBoss AS7 module, so it could be just grabbed and inserted to {{modules}} directory (similary to SnowDrop distribution [1]).
> It would allow to reuse RichFaces between projects and make the WARs really skinny for those who are deploying several RichFaces-based applications to the AS7.
> [1] https://docs.jboss.org/author/display/SNOWDROP/The+Spring+Deployer
--
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, 6 months
[JBoss JIRA] (RF-13288) EDT: sortOrder gets re-set when resizing a column
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina commented on RF-13288:
-------------------------------------
This would mean waiting untill WFK 2.4, right? I will check with the customer.
> EDT: sortOrder gets re-set when resizing a column
> -------------------------------------------------
>
> Key: RF-13288
> URL: https://issues.jboss.org/browse/RF-13288
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Labels: waiting_on_user
> Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
> <rich:extendedDataTable value="#{sandboxHandler.workItems}"
> keepSaved="true" var="workitem" id="table">
> <rich:column sortBy="#{workitem}"
> sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
> <f:facet name="header">
> <h:outputText value="bla" />
> <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
> sortBy="entryPD" render="table" />
> </f:facet>
> <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
> <f:param value="#{workitem}" />
> </h:outputFormat>
> </rich:column>
> </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.
--
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, 6 months
[JBoss JIRA] (RF-13288) EDT: sortOrder gets re-set when resizing a column
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13288:
----------------------------
Summary: EDT: sortOrder gets re-set when resizing a column (was: sortOrder gets re-set when resizing a column of extendedDataTable)
> EDT: sortOrder gets re-set when resizing a column
> -------------------------------------------------
>
> Key: RF-13288
> URL: https://issues.jboss.org/browse/RF-13288
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Labels: waiting_on_user
> Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
> <rich:extendedDataTable value="#{sandboxHandler.workItems}"
> keepSaved="true" var="workitem" id="table">
> <rich:column sortBy="#{workitem}"
> sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
> <f:facet name="header">
> <h:outputText value="bla" />
> <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
> sortBy="entryPD" render="table" />
> </f:facet>
> <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
> <f:param value="#{workitem}" />
> </h:outputFormat>
> </rich:column>
> </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.
--
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, 6 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13288:
---------------------------------
Hey Jonáš, I can confirm I have reproduced the issue with 4.3.2.
So I have tried to upgrade to 4.3.4 and the issue is fixed there.
Note that there were several commits /wrt EDT and state-saving since 4.3.2.
Could you try to upgrade to 4.3.4?
> sortOrder gets re-set when resizing a column of extendedDataTable
> -----------------------------------------------------------------
>
> Key: RF-13288
> URL: https://issues.jboss.org/browse/RF-13288
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
> <rich:extendedDataTable value="#{sandboxHandler.workItems}"
> keepSaved="true" var="workitem" id="table">
> <rich:column sortBy="#{workitem}"
> sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
> <f:facet name="header">
> <h:outputText value="bla" />
> <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
> sortBy="entryPD" render="table" />
> </f:facet>
> <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
> <f:param value="#{workitem}" />
> </h:outputFormat>
> </rich:column>
> </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.
--
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, 6 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned RF-13288:
-------------------------------
Assignee: Lukáš Fryč
> sortOrder gets re-set when resizing a column of extendedDataTable
> -----------------------------------------------------------------
>
> Key: RF-13288
> URL: https://issues.jboss.org/browse/RF-13288
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
> <rich:extendedDataTable value="#{sandboxHandler.workItems}"
> keepSaved="true" var="workitem" id="table">
> <rich:column sortBy="#{workitem}"
> sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
> <f:facet name="header">
> <h:outputText value="bla" />
> <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
> sortBy="entryPD" render="table" />
> </f:facet>
> <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
> <f:param value="#{workitem}" />
> </h:outputFormat>
> </rich:column>
> </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.
--
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, 6 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13288:
----------------------------
Labels: waiting_on_user (was: )
> sortOrder gets re-set when resizing a column of extendedDataTable
> -----------------------------------------------------------------
>
> Key: RF-13288
> URL: https://issues.jboss.org/browse/RF-13288
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Lukáš Fryč
> Labels: waiting_on_user
> Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
> <rich:extendedDataTable value="#{sandboxHandler.workItems}"
> keepSaved="true" var="workitem" id="table">
> <rich:column sortBy="#{workitem}"
> sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
> <f:facet name="header">
> <h:outputText value="bla" />
> <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
> sortBy="entryPD" render="table" />
> </f:facet>
> <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
> <f:param value="#{workitem}" />
> </h:outputFormat>
> </rich:column>
> </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.
--
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, 6 months
[JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13278:
-----------------------------
Environment:
java 7,
tomcat 7, JBoss AS,
mojarra, myfaces
chrome, firefox
was:
java 7,
tomcat 7, JBoss AS,
mojarra, myfaces
> rich:tab : label, placed in header-facet, can not be refreshed per ajax
> -----------------------------------------------------------------------
>
> Key: RF-13278
> URL: https://issues.jboss.org/browse/RF-13278
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.4
> Environment: java 7,
> tomcat 7, JBoss AS,
> mojarra, myfaces
> chrome, firefox
> Reporter: Alexey Shakov
>
> I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <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:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j"
> xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en">
> <h:head>
> </h:head>
> <h:body>
>
> <a4j:log hotkey="M" mode="popup" />
> <h:form id="form" prependId="false">
> <rich:tabPanel id="tabPanel">
> <rich:tab header="tab 1">
> <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" />
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> <h:outputText id="label" value="#{testBean.clicks} clicks" />
> </f:facet>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {code}
> testBean is a simple session-scoped HashMap.
--
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, 6 months
[JBoss JIRA] (RF-13278) rich:tab : label, placed in header-facet, can not be refreshed per ajax
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13278:
----------------------------------
I can confirm that it is a *regression* against _4.3.3.Final_.
However, it again *works* with _5.0.0-SNAPSHOT_.
* 4.3.4 reproduction bits
** [facelet|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/appl...]
** [bean|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/applica...]
** [test|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/ftest/s...]
* 5.0.0-SNAPSHOT
** just [facelet|https://github.com/richfaces/richfaces-qa/blob/master/metamer/app...] is different.
Steps to reproduce:
# build and deploy metamer
# load http://localhost:8080/metamer/faces/components/richTabPanel/rf-13278.xhtml
# click on the link in the first tab
# see that the header of the second tab is not updated
> rich:tab : label, placed in header-facet, can not be refreshed per ajax
> -----------------------------------------------------------------------
>
> Key: RF-13278
> URL: https://issues.jboss.org/browse/RF-13278
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.4
> Environment: java 7, tomcat 7, myfaces
> Reporter: Alexey Shakov
> Assignee: Juraj Húska
>
> I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <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:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j"
> xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en">
> <h:head>
> </h:head>
> <h:body>
>
> <a4j:log hotkey="M" mode="popup" />
> <h:form id="form" prependId="false">
> <rich:tabPanel id="tabPanel">
> <rich:tab header="tab 1">
> <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" />
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> <h:outputText id="label" value="#{testBean.clicks} clicks" />
> </f:facet>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {code}
> testBean is a simple session-scoped HashMap.
--
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, 6 months