voyent
RowSelectListener in 3.0  XML
Forum Index -> Development Build Feedback
Author Message
axlesoft


Joined: 06/Jan/2009 00:00:00
Messages: 189
Offline


For some reason my rowSelectListener that was working in 2.1beta 2 is no longer firing in 3.0.

Am I missing something?

Code:
    <ace:dialog id="next12daysWidget" minWidth="630" header="Next 12 days" modal="true" resizable="true" hideEffect="shrink" showEffect="grow" position="center" widgetVar="next12daysWidget">
 
                 <h:panelGroup>
                     <ace:dataTable selectionMode="single"   rowSelectListener="#{OrderWorkManager.dateRowSelectEvent}" id="next12DaysViewTable" value="#{OrderWorkManager.workEntries}" var="currentRow">
                         <ace:column  id="taskCol1">
 
                             <h:outputText  style="text-align:center" value="#{currentRow.dueDate}">
                                 <f:convertDateTime pattern="EE dd MMMM"/>
                             </h:outputText>
                             <f:facet name="header">
                                 <h:outputText id="listOutput" value="Work List"/>
                             </f:facet>
                         </ace:column>
 
                         <ace:column>
                             <h:outputText  style="text-align:center" value="#{currentRow.orderCount}"/>
                             <f:facet name="header">
                                 <h:outputText  value="Count"/>
                             </f:facet>
                             <f:facet name="footer">
                                 <h:outputText  style="text-align:center; font-size: 12pt; font-weight: bold" value="#{OrderWorkManager.totalOrderCount}">
                                     <f:convertNumber integerOnly="true"/>
                                 </h:outputText>
                             </f:facet>
 
                         </ace:column>
                         <ace:column>
                             <h:outputText  style="text-align:center" value="#{currentRow.AMCount}"/>
                             <f:facet name="header">
                                 <h:outputText  value="AM"/>
                             </f:facet>
                         </ace:column>
                         <ace:column>
                             <h:outputText style="text-align:center" value="#{currentRow.specificTimeCount}"/>
                             <f:facet name="header">
                                 <h:outputText  value="Timed"/>
                             </f:facet>
                         </ace:column>
                         <ace:column>
                             <h:outputText  style="text-align:center" value="#{currentRow.webCount}"/>
                             <f:facet name="header">
                                 <h:outputText  value="Web"/>
                             </f:facet>
                         </ace:column>
                         <ace:column >
                             <h:outputText  style="text-align:center" value="#{currentRow.totalValue}">
                                 <f:convertNumber type="currency"/>
                             </h:outputText>
                             <f:facet name="header">
                                 <h:outputText value="Value"/>
                             </f:facet>
                             <f:facet name="footer">
                                 <h:outputText style="text-align:center; font-size: 12pt; font-weight: bold" value="#{OrderWorkManager.workEntriesTotal}">
                                     <f:convertNumber type="currency"/>
                                 </h:outputText>
                             </f:facet>
 
                         </ace:column>
 
 
                     </ace:dataTable>
                 </h:panelGroup>
             </ace:dialog>
 


Thanks


Lee
nils.lundquist

Joined: 31/Aug/2010 11:18:29
Messages: 198
Offline


Hi Lee,

Thanks for bringing this to our attention, I believe this is the result of changes we've made to the distinction between 'passive' and 'active' selection using the table.

The table supports submitting selections and deselections passively, that is, storing them until submitted as part of an ajax request is initiated by another feature of the table, or during as part of communication initiated by another component in the view.

The alternative is active selection, which performs an ajax communication for every (de)selection. This was typically defined in beta 2 and prior with the 'update', 'rowSelectUpdate' and 'rowDeselectUpdate' properties which defined targets on the page to render during selection, and implied active selection.

However, active selection could also be implied by using a rowSelectListener as, of course, a server side listener requires a round trip. This has been missed in our new handling, which checks to see if there are any non-disabled ace:ajax tags applied to the component for the "select" event, and if so, enables 'active' selection, using the configuration of the ajax tag, or "select" event defaults.

To fix your issue in the short term, try adding Code:
<ace:ajax event="select" />
as a child to the table. This should trigger default active selection behaviour.

In the long term rowSelectListener will be patched to enable active selection, or the 'listener' available on the ace:ajax tag will be enhanced to provide event-specific information, like the rowSelectListener does currently. The ace:ajax listener, currently provides a generic AjaxBehaviourEvent to the listening method.

Hope that solves solve the issue for you and illuminates the behaviour of selection somewhat.

Nils
axlesoft


Joined: 06/Jan/2009 00:00:00
Messages: 189
Offline


That does the trick.

Thanks!
evgheni.sadovoi

Joined: 22/Aug/2011 11:28:32
Messages: 99
Offline


It is also reflected in our release notes page:

http://wiki.icefaces.org/display/ICE/ICEfaces+3.0.0.RC1+Release+Notes

ES
 
Forum Index -> Development Build Feedback
Go to:   
Powered by JForum 2.1.7ice © JForum Team