Details
- 
        Type:
 Bug
            
         - 
        Status: Closed
 - 
            Priority:
 Major
                
             - 
            Resolution: Fixed
 - 
            Affects Version/s: 3.0.RC1
 - 
            Component/s: ICE-Components
 - 
            Labels:None
 - 
            Environment:-
 
- 
                        Assignee Priority:P2
 
Description
                    The following issue has been reported:
The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.
Test case attached.
            
The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.
Test case attached.
Activity
| Field | Original Value | New Value | 
|---|---|---|
| Attachment | sf-10757.war [ 13848 ] | 
| Salesforce Case | [5007000000JOP3V] | |
| Description | 
                                                                The following issue has been reported: The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding.  | 
                
                                                               The following issue has been reported: The ace:dataExporter component searches from the UIViewRoot for the dataTable so it can't be used from within a composite component. It should do a findComponent() from itself so that it would find the datatable in its closest NamingContainer. Another improvement would be to also set the table component in a setter method so that it could used from a binding. Test case attached.  | 
                
| Fix Version/s | 3.0 [ 10241 ] | |
| Assignee Priority | P2 | |
| Assignee | Arturo Zambrano [ artzambrano ] | 
| Repository | Revision | Date | User | Message | 
| ICEsoft Public SVN Repository | #26844 | Tue Dec 13 08:58:40 MST 2011 | art.zambrano |      | 
| Files Changed | ||||
            					
			 
                            MODIFY
            				/icefaces3/trunk/icefaces/ace/component/src/org/icefaces/ace/component/dataexporter/DataExporter.java
            
             | 
| Status | Open [ 1 ] | Resolved [ 5 ] | 
| Resolution | Fixed [ 1 ] | 
| Fix Version/s | 3.0.RC2 [ 10313 ] | 
| Status | Resolved [ 5 ] | Closed [ 6 ] | 

Fixed at revision 26844.