[JBoss JIRA] Created: (RF-3899) Tree component doesn´t work with adviseNodeOpened, immediate="true" and switchType="ajax" or switchType="server"
by Mauricio Noda (JIRA)
Tree component doesn´t work with adviseNodeOpened, immediate="true" and switchType="ajax" or switchType="server"
----------------------------------------------------------------------------------------------------------------
Key: RF-3899
URL: http://jira.jboss.com/jira/browse/RF-3899
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: BEA Weblogic 9.2
Sun Facelets 1.1.14
Microsoft Internet Explorer 6.0.2900.2180 and Mozilla Firefox 2.0.0.15.
Reporter: Mauricio Noda
Tree component renders the tree incorrectly when adviseNodeOpened returns false in an initial request, but returns true in a subsequent request. The tree node expand icon shows as expanded, but the node children are not rendered.
Only happens when using immediate="true" and switchType set as "ajax" or "server". Works fine in client mode or when immediate is set to false.
Works but triggers unwanted validation errors when expanding/collapsing nodes:
<rich:tree adviseNodeOpened="#{bean.adviseNodeOpened}" changeExpandListener="#{bean.changeExpandListener}">
<!-- tree content -->
</rich:tree>
Works but is too slow with large trees:
<rich:tree immediate="true" switchType="client" adviseNodeOpened="#{bean.adviseNodeOpened}" changeExpandListener="#{bean.changeExpandListener}">
<!-- tree content -->
</rich:tree>
Initial request works, but subsequent requests doesn´t if adviseNodeOpened return changes:
<rich:tree immediate="true" adviseNodeOpened="#{bean.adviseNodeOpened}" changeExpandListener="#{bean.changeExpandListener}">
<!-- tree content -->
</rich:tree>
After some bugtracking, I found this:
Richfaces 3.2.1, inside org.richfaces.component.state.TreeState class, line 156, "return expandedNodes.contains(rowKey);" is ignoring expanded nodes queued in line 72 "queuedExpandedNodes.add(nextKey);" since it runs before line 278 "expandedNodes.addAll(queuedExpandedNodes);".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (RF-3953) columns: "filterMethod" doesn't work for dynamic columns.
by Mikhail Vitenkov (JIRA)
columns: "filterMethod" doesn't work for dynamic columns.
---------------------------------------------------------
Key: RF-3953
URL: https://jira.jboss.org/jira/browse/RF-3953
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: ie6, ie7, ff 3.0, safari 3.1, opera 9.5(3.2.2.BETA1)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Step 1. Add filterMethod to bean:
public boolean filterMethod(Object obj) {
Data d = (Data)obj;
if(d.getStr0().startsWith(filterInput)) return true;
return false;
}
filterInput is a String value.
Step 2. Bind rich:columns with method listed above through the 'filterMethod' attribute.
<rich:columns filterMethod="#{columns.filterMethod}"...
Step 3. Add input field for "filterInput" value defined in Step 1:
<h:outputText value="filterMethod"></h:outputText>
<h:inputText value="#{columns.filterInput}"
onchange="submit();" />
Step 4. Navigate to page contained tested dynamic columns.
Step 5. Enter something in "filterMethod" input & click mouse out.
Actual behavior:
Filter method doesn't work. Data in rich:columns remains previous.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months
[JBoss JIRA] Created: (RF-4006) pickList requiredMessage does not take effect
by krystan honour (JIRA)
pickList requiredMessage does not take effect
---------------------------------------------
Key: RF-4006
URL: https://jira.jboss.org/jira/browse/RF-4006
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1, 3.2.0.SR1, 3.2.0
Environment: Windows XP/W2K3, IE 6.x, IE 7.x, Mozilla Firefox
Reporter: krystan honour
When setting the requiredMessage on the pickList component with the required attribute set to "true" the requiredMessage, whether hardcoded or an expression does not override the global validators message.
Test code is as follows:
<rich:pickList id="testList"
copyAllControlLabel="Add All"
copyControlLabel="Add"
listsHeight="90"
sourceListWidth="200"
targetListWidth="200"
required="true"
requiredMessage="Error input is required.">
<f:selectItem itemLabel="Human Resources" itemValue="1"/>
<f:selectItem itemLabel="Product Development" itemValue="2"/>
<f:selectItem itemLabel="Marketing" itemValue="3"/>
<f:selectItem
itemLabel="Sales" itemValue="4"/>
</rich:pickList>
This functionality works for other rich components and is affecting a live development.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 7 months