[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12033:
------------------------------------
[~cc2000] do you observe it /only/ in IE8?
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> ----------------------------------------------------------------------
>
> Key: RF-12033
> URL: https://issues.jboss.org/browse/RF-12033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.0.Final
> Environment: FireFox 10.0.2 (works in IE7)
> GlassFish 3.1
> Reporter: Josh Hill
> Labels: lazy-loaded
> Fix For: 5-Tracking
>
> Attachments: richfaces-test.zip
>
>
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> Facelet file from the attached testcase:
> {code}
> <?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:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:f="http://java.sun.com/jsf/core">
> <h:head>
> <title>Test One</title>
> </h:head>
> <h:body>
> <p>Extended datatable inside tabpanel with switchType "client"</p>
> <h:form>
> <rich:tabPanel switchType="client">
> <rich:tab>
> <f:facet name="header">
> Tab One
> </f:facet>
> Tab One
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> Tab Two
> </f:facet>
> <rich:extendedDataTable value="#{colorsBean.colors}" var="color">
> <rich:column>
> <f:facet name="header">
> Column 1
> </f:facet>
> #{color}
> </rich:column>
> </rich:extendedDataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {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, 8 months
[JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13101:
-------------------------------
Labels: rich:select select waiting_on_user (was: rich:select select)
> rich:select Method getSelectInputLabel is not working when using objects
> ------------------------------------------------------------------------
>
> Key: RF-13101
> URL: https://issues.jboss.org/browse/RF-13101
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, component-selects
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Reporter: J W
> Labels: rich:select, select, waiting_on_user
> Fix For: 4.5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different.
> The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround).
--
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, 8 months
[JBoss JIRA] (RF-12033) ExtendedDataTable doesn't show up in tabpanel with switchType="client"
by Steve Oh (JIRA)
[ https://issues.jboss.org/browse/RF-12033?page=com.atlassian.jira.plugin.s... ]
Steve Oh commented on RF-12033:
-------------------------------
I observed the problem with 4.3.4.FINAL on IE8.
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> ----------------------------------------------------------------------
>
> Key: RF-12033
> URL: https://issues.jboss.org/browse/RF-12033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.0.Final
> Environment: FireFox 10.0.2 (works in IE7)
> GlassFish 3.1
> Reporter: Josh Hill
> Labels: lazy-loaded
> Fix For: 5-Tracking
>
> Attachments: richfaces-test.zip
>
>
> ExtendedDataTable doesn't show up in tabpanel with switchType="client"
> Facelet file from the attached testcase:
> {code}
> <?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:h="http://java.sun.com/jsf/html"
> xmlns:rich="http://richfaces.org/rich"
> xmlns:f="http://java.sun.com/jsf/core">
> <h:head>
> <title>Test One</title>
> </h:head>
> <h:body>
> <p>Extended datatable inside tabpanel with switchType "client"</p>
> <h:form>
> <rich:tabPanel switchType="client">
> <rich:tab>
> <f:facet name="header">
> Tab One
> </f:facet>
> Tab One
> </rich:tab>
> <rich:tab>
> <f:facet name="header">
> Tab Two
> </f:facet>
> <rich:extendedDataTable value="#{colorsBean.colors}" var="color">
> <rich:column>
> <f:facet name="header">
> Column 1
> </f:facet>
> #{color}
> </rich:column>
> </rich:extendedDataTable>
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> </h:body>
> </html>
> {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, 8 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13250:
-------------------------------
Affects Version/s: 4.3.5
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4, 4.3.5
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Juraj Húska
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
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, 8 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reopened RF-13250:
--------------------------------
Assignee: Juraj Húska (was: Pavol Pitonak)
[~sebek64], thanks for all the information you provided. We'll try to reproduce it.
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Juraj Húska
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
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, 8 months
[JBoss JIRA] (RF-13550) Refactor bridge-base so that it will allow bridges to extend widgets
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13550?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13550.
-----------------------------
Assignee: Brian Leathem
Resolution: Rejected
Ok, agree, I'm rejecting this request then.
> Refactor bridge-base so that it will allow bridges to extend widgets
> --------------------------------------------------------------------
>
> Key: RF-13550
> URL: https://issues.jboss.org/browse/RF-13550
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Brian Leathem
>
> This will allow bridges to extend widget API and make it more natural for JSF users, e.g.:
> Editor is now:
> {code}
> $.widget('rf.editorBridge', $.rf.bridgeBase,
> {code}
> but we want:
> {code}
> $.widget('rf.editorBridge', $.rich.editor,
> {code}
> On multiple inheritance in jQuery Widget Factory:
> https://forum.jquery.com/topic/how-to-extend-a-widget-factory-widget-with...
> The way of extending API should be designed in that way that user calls e.g.:
> {code}
> #{r:component('editor')}.setValue();
> {code}
> but editor has (or rather should have) only a method which is named in jQuery Widget Factory style:
> {code}
> data('editor').value() / data('editor').value(newValue)
> editor('value') / editor('value', newValue)
> {code}
> So, we want bridge to add the setValue/getValue API:
> {code}
> $.extend(widget), { setValue: ..., getValue: ...};
> {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, 8 months
[JBoss JIRA] (RF-13550) Refactor bridge-base so that it will allow bridges to extend widgets
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13550?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13550:
------------------------------------
I spent some time playing with this in various scenarios and I've concluded it's not a good idea. We end up losing what is currently a good encapsulation of concerns and end up polluting our widget object with bridge functionality. I much prefer keeping these ideas separate.
Going back to the original problem of providing legacy functions without polluting the widget, this /can/ instead be done by "monkey patching" the widget prototype in the bridge js file. However this presents it's own concerns in terms of properly documenting the widget capabilities.
Instead we should just make take a clean start with the js API for 5.0 and do things correctly. The RF 4 js API was not well standardized across components and was poorly documented. I don't believe we will break many applications with any naming changed in the RF 5 js API.
> Refactor bridge-base so that it will allow bridges to extend widgets
> --------------------------------------------------------------------
>
> Key: RF-13550
> URL: https://issues.jboss.org/browse/RF-13550
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> This will allow bridges to extend widget API and make it more natural for JSF users, e.g.:
> Editor is now:
> {code}
> $.widget('rf.editorBridge', $.rf.bridgeBase,
> {code}
> but we want:
> {code}
> $.widget('rf.editorBridge', $.rich.editor,
> {code}
> On multiple inheritance in jQuery Widget Factory:
> https://forum.jquery.com/topic/how-to-extend-a-widget-factory-widget-with...
> The way of extending API should be designed in that way that user calls e.g.:
> {code}
> #{r:component('editor')}.setValue();
> {code}
> but editor has (or rather should have) only a method which is named in jQuery Widget Factory style:
> {code}
> data('editor').value() / data('editor').value(newValue)
> editor('value') / editor('value', newValue)
> {code}
> So, we want bridge to add the setValue/getValue API:
> {code}
> $.extend(widget), { setValue: ..., getValue: ...};
> {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, 8 months
[JBoss JIRA] (RF-13436) Upgrade CKEditor to 4.3
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13436?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13436.
-----------------------------
Labels: needs-qe (was: rich_editor)
Resolution: Done
The CKEditor was switched to use CKEditor 4 distributed in RichWidgets project.
[~ppitonak] could you please start QE process for the component upgrade?
Note that the whole component underwent general re-implementation using jQuery Widget Factory, etc. but the API stays same.
We need to cover and expand test suite:
* re-test with Metamer
* [expand RichWidgets tests suite|https://github.com/richwidgets/richwidgets/issues/179] (just few basic tests there)
* add few basic framework tests (should use Page Fragment)
Pavol, could you please open appropriate RFPL/QE JIRAs?
> Upgrade CKEditor to 4.3
> -----------------------
>
> Key: RF-13436
> URL: https://issues.jboss.org/browse/RF-13436
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4, 5.0.0.Alpha1
> Reporter: barbara b
> Assignee: Lukáš Fryč
> Labels: needs-qe
> Fix For: 5.0.0.Alpha4
>
>
> All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor.
--
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, 8 months