October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13232?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-13232: ----------------------------- Assignee: Juraj Húska > Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment > -------------------------------------------------------------------------------------------------- > > Key: RF-13232 > URL: https://issues.jboss.org/browse/RF-13232 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Minor > > This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian. > It matters to the {{CoreDeployment}} and to the similar. > Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class. > Here comes the problem with multiple deployments, when each deployed archive has to have different name. > Proposed solution: > Add overloaded constructor method, which would take a name for the deployed archive. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13233?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13233: ------------------------------------ QE: this change is meant to be idempotent, and no existing functionality should change. [~lfryc] please perform a sanity check on the commits to the richfaces and cdk repositories. > Support attribute mapping for cdk:scriptOption > ---------------------------------------------- > > Key: RF-13233 > URL: https://issues.jboss.org/browse/RF-13233 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: cdk-4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The syntax for cdk:passThrough attributes supports attribute mapping: > {code} > cdk:passThrough="onclick:onlistclick ..." > {code} > It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: > {code} > <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13233?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13233. -------------------------------- Resolution: Done > Support attribute mapping for cdk:scriptOption > ---------------------------------------------- > > Key: RF-13233 > URL: https://issues.jboss.org/browse/RF-13233 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: cdk-4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The syntax for cdk:passThrough attributes supports attribute mapping: > {code} > cdk:passThrough="onclick:onlistclick ..." > {code} > It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: > {code} > <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13233?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13233: ------------------------------- Labels: needs-qe (was: ) > Support attribute mapping for cdk:scriptOption > ---------------------------------------------- > > Key: RF-13233 > URL: https://issues.jboss.org/browse/RF-13233 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: cdk-4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The syntax for cdk:passThrough attributes supports attribute mapping: > {code} > cdk:passThrough="onclick:onlistclick ..." > {code} > It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: > {code} > <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13233?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13233: ------------------------------------ The change required to the CDK to enable this feature is rather innocuous. The _AddAttributesToScriptHashStatement_ class uses the _PassThrough_ to parse and hold the attribute names, which already has support for the "html" attribute name, and the "component" attribute name. In the current implementation they are just set to the same value. As such, introducing a split operation on the ":" character, and then falling back to setting the attribute names to be the same when no split is performed will leave the change idempotent for all existing use cases. However, to make this work a change is required in the RenderkitUtils#addToScriptHash method, where the componentAttributeName is used instead of the htmlAttributeName. This has worked fine until now as the values have been the same for all scriptOptions. The change introduced to the CDK in this issue however allows for them to be different, and so the correct attribute name has to be used. > Support attribute mapping for cdk:scriptOption > ---------------------------------------------- > > Key: RF-13233 > URL: https://issues.jboss.org/browse/RF-13233 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: cdk-4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The syntax for cdk:passThrough attributes supports attribute mapping: > {code} > cdk:passThrough="onclick:onlistclick ..." > {code} > It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: > {code} > <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13233?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13233: ------------------------------- Description: The syntax for cdk:passThrough attributes supports attribute mapping: {code} cdk:passThrough="onclick:onlistclick ..." {code} It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: {code} <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> {code} was: The syntax for cdk:passThrough attributes supports attribute mapping: {code} cdk:passThrough="onclick:onlistclick ..." {code} It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: {code} <cdk:scriptOption wrapper="eventHandler" attributes="onchange:change ..." /> {code} > Support attribute mapping for cdk:scriptOption > ---------------------------------------------- > > Key: RF-13233 > URL: https://issues.jboss.org/browse/RF-13233 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: cdk-4.5.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The syntax for cdk:passThrough attributes supports attribute mapping: > {code} > cdk:passThrough="onclick:onlistclick ..." > {code} > It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: > {code} > <cdk:scriptOption wrapper="eventHandler" attributes="change:onchange ..." /> > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13233) Support attribute mapping for cdk:scriptOption

by Brian Leathem (JIRA)

Brian Leathem created RF-13233: ---------------------------------- Summary: Support attribute mapping for cdk:scriptOption Key: RF-13233 URL: https://issues.jboss.org/browse/RF-13233 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: cdk Reporter: Brian Leathem Assignee: Brian Leathem Fix For: cdk-4.5.0.Alpha2 The syntax for cdk:passThrough attributes supports attribute mapping: {code} cdk:passThrough="onclick:onlistclick ..." {code} It would be nice if the cdk:scriptOption supported similar attribute mapping, as in: {code} <cdk:scriptOption wrapper="eventHandler" attributes="onchange:change ..." /> {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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13230: ------------------------------- Labels: regression (was: ) > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Labels: regression > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13230: ---------------------------------- Assignee: Pavol Pitonak Pavol, can you create some tests to check if this is indeed a regression? > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13230: ------------------------------- Fix Version/s: 4.3.5 > Resetting table state on extendedDataTable does not reset table when using ajax re-render > ----------------------------------------------------------------------------------------- > > Key: RF-13230 > URL: https://issues.jboss.org/browse/RF-13230 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Labels: regression > Fix For: 4.3.5 > > > On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form. > To reproduce: > rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same. > This used to work on RF 4.3.3 -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues October 2013