[JBoss JIRA] Created: (RF-3764) Calendar: ValueChangeListener called twice on first request only.
by Ilya Shaikovsky (JIRA)
Calendar: ValueChangeListener called twice on first request only.
-----------------------------------------------------------------
Key: RF-3764
URL: http://jira.jboss.com/jira/browse/RF-3764
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Reporter: Ilya Shaikovsky
Assigned To: Nick Belaevski
I'm using
<rich:calendar value="#{calendarBean.selectedDate}"
popup="false" showApplyButton="false"
cellWidth="120px" cellHeight="120px"
boundaryDatesMode="none" showWeeksBar="false"
dataModel="#{calendarDataModel}" oncurrentdateselect="return false" id="calendar" valueChangeListener="#{calendarDataModel.valueChanged}">
<f:facet name="header">
<h:outputText value="{currentMonthControl}"/>
</f:facet>
<a4j:outputPanel layout="block" id="cell">
<h:panelGrid columns="1">
<h:outputText value="{day}" style="align:center"/>
<h:outputText value="{data.shortDescription}"/>
<h:outputText value="{data.description}"/>
</h:panelGrid>
</a4j:outputPanel>
<a4j:support event="onchanged" oncomplete="#{rich:component('panel')}.show()" reRender="editContent"/>
</rich:calendar>
So after I select the date first time - I could see in debug that my valueChangeListener called twice - first time newValue is ok and the second time - its' wrong.
After all next requests all is fine.
Nick I want to add organiser sample to demo till release. So could you fix this in this release?
I've asked Alex Kushunin and checked the rendererBase code and think you need to review next code:
if (currentDateString != null) {
CurrentDateChangeEvent ev = new CurrentDateChangeEvent(component,
currentDateString);
ev.setPhaseId(PhaseId.PROCESS_VALIDATIONS);
ev.queue();
// TODO nick - nick - queue this event when ValueChangeEvent is
// queued?
new AjaxEvent(component).queue();
}
--
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
15 years, 10 months
[JBoss JIRA] Created: (RF-3791) dataScroller: problem with sorting of rich:dataTable contained rich:dataScroller component inside.
by Mikhail Vitenkov (JIRA)
dataScroller: problem with sorting of rich:dataTable contained rich:dataScroller component inside.
--------------------------------------------------------------------------------------------------
Key: RF-3791
URL: http://jira.jboss.com/jira/browse/RF-3791
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.2
Environment: IE6, IE7, FF, Opera, Safari
Reporter: Mikhail Vitenkov
Assigned To: Konstantin Mishin
Step 1. Add dataScroller component inside rich:dataTable, supported sorting & filtering features, following way:
<rich:dataTable id="dataTableId" value="#{dataScroller.dataTable}"... >
<f:facet name="header">
<rich:datascroller ajaxSingle="#{dataScroller.ajaxSingle}" ...>
...
</rich:datascroller>
</f:facet>
<f:facet name="footer">
</f:facet>
<rich:column sortBy="#{dT.data0}" filterBy="#{dT.data0}" filterEvent="onchange">
<h:outputText value="#{dT.data0}" />
</rich:column>
<rich:column sortBy="#{dT.data1}" filterBy="#{dT.data1}" filterEvent="onchange">
<h:outputText value="#{dT.data1} " />
</rich:column>
</rich:dataTable>
Step 2. Navigate on the page.
Step 3. Navigate to the 3rd page using dataScroller.
Step 4. Click on sorting icon("Ascending").
Step 5. Verify dataTable columns' content currently displayed.
Step 6. Click on "Next" dataScroller link & verify the number of page being displayed.
Actual behavior:
Step 5: 3rd datatable page contained 10 page's content;
Step 6: after "Next" is clicked - 11th page is displayed instead of 4th.
--
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
15 years, 10 months