[JBoss JIRA] (RF-12894) The richfaces-framework is not reloadable by JRebel
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12894?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-12894.
-----------------------------
Assignee: Lukáš Fryč
Fix Version/s: (was: 5.0.0.Alpha3)
Resolution: Out of Date
> The richfaces-framework is not reloadable by JRebel
> ---------------------------------------------------
>
> Key: RF-12894
> URL: https://issues.jboss.org/browse/RF-12894
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: third-party
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> It seems when you compile the framework with CDK, the faces-config.xml is re-generated and re-loaded by JRebel.
> However the other configuration files stored in {{META-INF/}} (e.g. [core.faces-config.xml|https://github.com/richfaces/richfaces5/blob/master...]) directly (without CDK processing) are not taken into consideration in reloaded configuration, thus this configuration is ignored. As the result, no Core configuration is loaded and no RichFaces Core feature does work.
> ----
> The JRebel reload and quick turnaround is one of the features we wanted to enable by build re-structure thus I consider this high priority to cooperate with JRebel team and make it work.
--
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, 9 months
[JBoss JIRA] (RF-12894) The richfaces-framework is not reloadable by JRebel
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12894?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12894:
---------------------------------
I believe this issue was fixed with resolution of RF-13074.
> The richfaces-framework is not reloadable by JRebel
> ---------------------------------------------------
>
> Key: RF-12894
> URL: https://issues.jboss.org/browse/RF-12894
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: third-party
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> It seems when you compile the framework with CDK, the faces-config.xml is re-generated and re-loaded by JRebel.
> However the other configuration files stored in {{META-INF/}} (e.g. [core.faces-config.xml|https://github.com/richfaces/richfaces5/blob/master...]) directly (without CDK processing) are not taken into consideration in reloaded configuration, thus this configuration is ignored. As the result, no Core configuration is loaded and no RichFaces Core feature does work.
> ----
> The JRebel reload and quick turnaround is one of the features we wanted to enable by build re-structure thus I consider this high priority to cooperate with JRebel team and make it work.
--
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, 9 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. commented on RF-13126:
--------------------------------
I have been able to render using table state such that only truly represented columns (no zero width entries) are specified in the columnsWidthState (yeah!) - and things appear to be functioning properly using 5.0 Alpha 1. The one remaining problem I do continue to see, however, is the issue where the column header dividers used to resize are often misaligned with the location of the column divider in the data below. It appears there may be some miscalculation of the size such that the width of the column header is greater than the width of the data in the column below.
Thanks!
Steve
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be RF-4855 + RF-13094 and RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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, 9 months
[JBoss JIRA] (RF-13190) Support Atmosphere-over-WebSockets with WildFly/Undertow
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13190?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13190:
-------------------------------
Original Estimate: 45 minutes
Remaining Estimate: 45 minutes
> Support Atmosphere-over-WebSockets with WildFly/Undertow
> --------------------------------------------------------
>
> Key: RF-13190
> URL: https://issues.jboss.org/browse/RF-13190
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> This is tracking issue which should help us to leverage websockets via new undertow module.
> Note that it's on upstream projects to implement the functionality, we should test it, coordinate with upstream and upgrade to relevant versions.
--
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, 9 months
[JBoss JIRA] (RF-12292) "this" in oncomplete of a4j:commandButton returns window object.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12292?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12292:
-------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> "this" in oncomplete of a4j:commandButton returns window object.
> ----------------------------------------------------------------
>
> Key: RF-12292
> URL: https://issues.jboss.org/browse/RF-12292
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final
> Environment: Windows XP SP3, Weblogic 10.3.5, JSF 2.0.4, RF 4.2.2 Final
> Reporter: Nikolai Alexeev
> Assignee: Lukáš Fryč
> Priority: Minor
> Labels: a4j_commandbutton
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> When using "this" operator in oncomplete attribute of a4j:commandButton user gets window object instead of expected button object. In RF3 everything was as expected.
--
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, 9 months
[JBoss JIRA] (RF-13183) Autocomplete: behavior of component with tokens changed
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13183?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13183:
-------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> Autocomplete: behavior of component with tokens changed
> -------------------------------------------------------
>
> Key: RF-13183
> URL: https://issues.jboss.org/browse/RF-13183
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, regression
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved)
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # select Alabama
> result:
> * output contains "Alabama," but should be "Alabama"
> * it would output "Alabama" in 5.0.0.Alpha1
> * this behavior is influenced by "tokens" attribute
--
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, 9 months
[JBoss JIRA] (RF-13181) Autocomplete: suggestion list is not valid HTML code
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13181?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13181:
-------------------------------
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
> Autocomplete: suggestion list is not valid HTML code
> ----------------------------------------------------
>
> Key: RF-13181
> URL: https://issues.jboss.org/browse/RF-13181
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # check suggestion list's markup
> result:
> * Autocomplete generates an unsorted list (ul) with several list items (li), one for each suggestion. However, inside each li, there is yet another li which is not allowed by HTML.
> {code:xml}
> <ul class="ui-autocomplete ui-menu ui-widget ui-widget-content ui-corner-all" id="ui-id-1" tabindex="0" style="z-index: 1; display: block; top: 237.0142364501953px; left: 10px; width: 161px;">
> <li class="ui-menu-item" role="presentation">
> <a id="ui-id-7" class="ui-corner-all" tabindex="-1">
> <li>Alabama</li>
> </a>
> </li>
> ...
> </ul>
> {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
10 years, 9 months
[JBoss JIRA] (RF-13182) Autocomplete: attributes style and styleClass missing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13182?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13182:
-------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> Autocomplete: attributes style and styleClass missing
> -----------------------------------------------------
>
> Key: RF-13182
> URL: https://issues.jboss.org/browse/RF-13182
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, regression
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Component autocomplete is missing two attributes - style and styleClass. There attributes were present in 5.0.0.Alpha1.
--
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, 9 months