[JBoss JIRA] Created: (RF-9426) Check iteration state saving for facets of dataTable component
by Nick Belaevski (JIRA)
Check iteration state saving for facets of dataTable component
---------------------------------------------------------------
Key: RF-9426
URL: https://jira.jboss.org/browse/RF-9426
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component-tables, performance
Affects Versions: 4.0.0.Milestone3
Reporter: Nick Belaevski
Assignee: Konstantin Mishin
Fix For: 4.0.0.Milestone4
Here is the excerpt from the letter I've just received:
>>>> There is memory leak in UIDataAdaptorBase/rich:dataTable.
>>>> It affects:
>>>> - external filtering (input in "header" facet)
>>>> - embedded filtering ("filterBy" column attribute) - facet
>>>> "filterValueInput" is added internally
>>>>
>>>> Code in UIDataAdaptorBase#saveChildState:
>>>> itr = c.getFacets().values().iterator();
>>>> while (itr.hasNext()) {
>>>> saveChildState(faces, (UIComponent) itr.next(), childState);
>>>> }
>>>>
>>>> Column facet state is saved in the view for each row.
>>>>
>>>> For the table with 500 rows 5 columns with filtering that resulst in
>>>> 350kB
>>>> of extra view size.
>>>> UIDataAdaptorBase$DataState size - 350 kB
>>>> There are 2500 (500 rows * 5 columns) instances of
>>>> UIDataAdaptorBase$SavedState.
>>>>
>>>> The same table without filtering does not have this issue and
>>>> UIDataAdaptorBase$DataState size is 1 kB.
>>>>
This affects 3.x. Please check if 4.x is affected by the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (RF-10825) ClientBehavior: view state is not saved if behavior is marked to hold initial state
by Nick Belaevski (JIRA)
ClientBehavior: view state is not saved if behavior is marked to hold initial state
-----------------------------------------------------------------------------------
Key: RF-10825
URL: https://issues.jboss.org/browse/RF-10825
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: architectural
Affects Versions: 4.0.0.Final
Reporter: Nick Belaevski
ClientBehavior contains the following code:
{noformat} @Override
public Object saveState(FacesContext context) {
Object[] state = null;
Object parentState = super.saveState(context);
if (initialStateMarked()) {
if (parentState != null) {
state = new Object[] { parentState };
}
} else {
Object savedHelper = null;
if(behaviorStateHelper != null) {
savedHelper = behaviorStateHelper.saveState(context);
}
state = new Object[3];
state[0] = parentState;
state[1] = savedHelper;
state[2] = saveBindings(context, bindings);
}
return state;
}{noformat}
however state of state helper should be saved even if initialStateMarked() is returning true.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (RF-10888) Datascroller: incompatibility with sorting feature
by Nick Belaevski (JIRA)
Datascroller: incompatibility with sorting feature
--------------------------------------------------
Key: RF-10888
URL: https://issues.jboss.org/browse/RF-10888
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Nick Belaevski
Priority: Critical
When data scroller is used together with filtering, it's always one step behind of filtered value due to model not being reset when row count is being requested.
<it:dataTable keepSaved="true" id="richTable" var="record" value="#{personBean.dataModel}" rows="20">
<ui:include src="column.xhtml">
<ui:param name="property" value="name" />
</ui:include>
<ui:include src="column.xhtml">
<ui:param name="property" value="surname" />
</ui:include>
<ui:include src="column.xhtml">
<ui:param name="property" value="email" />
</ui:include>
<f:facet name="footer">
<it:dataScroller id="scroller" />
</f:facet>
</it:dataTable>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (RF-10885) Using rich:progressBar on a page breaks f:ajax onevent
by Adrian Meredith (JIRA)
Using rich:progressBar on a page breaks f:ajax onevent
------------------------------------------------------
Key: RF-10885
URL: https://issues.jboss.org/browse/RF-10885
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 4.0.0.Final
Environment: glassfish 3.1 mojarra 2.1
Reporter: Adrian Meredith
When using rich:progress bar on a page onevent no longer functions the same way. When using mojarra onevent takes the name of a js function that takes one parameter (data). After inserting a rich component on the page onevent now requires attributes breaking compatability with standard jsf (and introducing untold amount of unpredictable bugs).
mojarra :
<f:ajax onevent="doValidateMessages"/>
richfaces:
<f:ajax onevent="doValidateMessages()"/>
This means i have to use diffent syntax depending on whether i'm using richfaces on a particular page!! This is already a well established jsf2 application so rewriting it using the aforementioned workaround isn't very practical.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (RF-9727) Using rich:editor + spellchecker plugin + a4j:poll doesn't work right
by Chris Dollar (JIRA)
Using rich:editor + spellchecker plugin + a4j:poll doesn't work right
---------------------------------------------------------------------
Key: RF-9727
URL: https://jira.jboss.org/browse/RF-9727
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, component-push/poll
Affects Versions: 3.3.3.Final
Environment: Linux, JBoss 4.2.2.GA, Richfaces-3.3.3.Final
Reporter: Chris Dollar
Using the "spellchecker" plugin for the rich:editor (which is distributed with the RF library) does not work correctly when used on a page that contains an a4j:poll. When the a4j:poll action fires any spellcheck information in the rich:editor is lost. The forum link listed has more details about the issue and how the spellchecker plugin is supposed to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months