[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13288:
--------------------------------
Description:
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.
was:
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 to show the behaviour.
> 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
11 years, 2 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13288:
--------------------------------
Steps to Reproduce:
1. Open the reproducer in your IDE of choice (should be capable of debugging)
2. Set breakpoint at SortingBean.LogMap.put and run the application
3. Go to [app_host]/exttable_reproducer/sandbox.xhtml
4. Try sorting the column by clickng the arrows, note that only SortingBean is touching the map
5. Resize the column and try sorting it again, note that after SortingBean is finished, ELResolver sets sortsOrders['entryPD'] to the original value.
was:
1. Open the reproducer in your IDE of choice (should be capable of debugging)
2. Set breakpoint at SortingBean.LogMap.put and run the application
3. Go to #{app_host}/exttable_reproducer/sandbox.xhtml
4. Try sorting the column by clickng the arrows, note that only SortingBean is touching the map
5. Resize the column and try sorting it again, note that after SortingBean is finished, ELResolver sets sortsOrders['entryPD'] to the original value.
> 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
11 years, 2 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Jonáš Trantina (JIRA)
[ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.s... ]
Jonáš Trantina updated RF-13288:
--------------------------------
Attachment: reproducer.tar.gz
> 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 to show 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
11 years, 2 months
[JBoss JIRA] (RF-13288) sortOrder gets re-set when resizing a column of extendedDataTable
by Jonáš Trantina (JIRA)
Jonáš Trantina created RF-13288:
-----------------------------------
Summary: 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
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 to show 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
11 years, 2 months
[JBoss JIRA] (RF-13287) rich:extendedDataTable column resizing with ajax loading not working properly
by Andreas G (JIRA)
Andreas G created RF-13287:
------------------------------
Summary: rich:extendedDataTable column resizing with ajax loading not working properly
Key: RF-13287
URL: https://issues.jboss.org/browse/RF-13287
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.3.4
Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
Reporter: Andreas G
In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
Reproducible in the 4.3.4 showcase!
--
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
11 years, 2 months
[JBoss JIRA] (RF-10646) Css in composite components not found with MyFaces
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-10646?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-10646:
------------------------------------
Yes, it is a MyFaces issue.
> Css in composite components not found with MyFaces
> --------------------------------------------------
>
> Key: RF-10646
> URL: https://issues.jboss.org/browse/RF-10646
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.0.0.CR1, 4.2.2.Final, 4.3.4
> Environment: RichFaces 4.0.0-SNAPSHOT SVN r.21968
> MyFaces 2.0.5-SNAPSHOT (and all older versions)
> Tomcat 6.0.29
> all browsers
> RichFaces 4.2.2.Final
> Metamer 4.2.2.Final
> Apache MyFaces JSF-2.1 Core Impl 2.1.5
> Apache Tomcat 7.0.26
> all browsers
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Attachments: cc.zip, compositecomponent.war, RF-10646.zip
>
>
> MyFaces cannot load the stylesheet for the following page with a composite component (the text is black instead of fuchsia). When RichFaces is removed from project, everything works fine (see attached project for Tomcat).
> Mar 1, 2011 3:49:48 PM org.richfaces.resource.ResourceFactoryImpl logResourceProblem
> WARNING: Resource text.ecss?db=eAHL6rC8BQAEkAIG&ln=my%252fcss was not found
> {code:title=index.xhtml|borderStyle=solid}
> <!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:h="http://java.sun.com/jsf/html" xmlns:my="http://java.sun.com/jsf/composite/my" >
> <h:head/>
> <h:body>
> <my:colorText text="Hello World!"/>
> </h:body>
> </html>
> {code}
> {code:title=resources/my/colorText.xhtml|borderStyle=solid}
> <!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:h="http://java.sun.com/jsf/html"
> xmlns:composite="http://java.sun.com/jsf/composite" >
> <h:body>
> <composite:interface>
> <composite:attribute name="text" type="java.lang.String" required="true" />
> </composite:interface>
> <composite:implementation>
> <h:outputStylesheet library="my/css" name="text.ecss"/>
> <h:outputText id="text" value="#{cc.attrs.text}" styleClass="color-text" />
> <br/><br/>
> </composite:implementation>
> </h:body>
> </html>
> {code}
> {code:title=resources/my/css/text.ecss|borderStyle=solid}
> .color-text {
> color: fuchsia;
> text-weight: bold;
> }
> {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
11 years, 2 months
[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13082:
------------------------------------
The easiest way to see what attributes are currently imple'd in a component is to build the _dist_ module with the _release_. Looking at that doc I can see that I have not removed the unused attributes from the parent class _AbstractOrderingComponent_. I've filed RF-13286 to address the removal of the now obsolete attributes.
> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
> Key: RF-13082
> URL: https://issues.jboss.org/browse/RF-13082
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Labels: needs-qe
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listHeight
> * listWidth
> * listMaxHeight
> * listMaxWidth
> It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the height/width CSS attributes are better set with CSS styles, rather than via facelet attributes.
> Additionally, we should consider dropping the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover?
--
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
11 years, 2 months
[JBoss JIRA] (RF-13286) Remove the deprecated attributes from the AbstractOrderingComponent parent class
by Brian Leathem (JIRA)
Brian Leathem created RF-13286:
----------------------------------
Summary: Remove the deprecated attributes from the AbstractOrderingComponent parent class
Key: RF-13286
URL: https://issues.jboss.org/browse/RF-13286
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component-selects
Affects Versions: 5.0.0.Alpha2
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 5.0.0.Alpha2
The _AbstractOrderingComponent_ parent class defines attributes common to the orderingList and pickList components. This issue addresses the removal of the attributes as defined by the issues RF-13082 and RF-13083.
While removing these attributes, investigate if the _AbstractOrderingComponent_ class could be better represented as a *Props interface.
--
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
11 years, 2 months