Committed improvement at revision 30649 in the trunk.
Note: since the ace:dataExporter component has always worked by creating a new instance of a specific exporter type, the best practice for a custom exporter is to return a new instance of the exporter in the getter method, e.g.:
public Object getCustomExporter()
{
return new MyExporter();
}
Since, this getter is called in the Invoke Application phase, the exporter instance can pass any other application data in the constructor of the custom exporter, e.g.:
public Object getCustomExporter()
{
return new MyExporter(selectedItems);
}
Committed improvement at revision 30649 in the trunk.
Note: since the ace:dataExporter component has always worked by creating a new instance of a specific exporter type, the best practice for a custom exporter is to return a new instance of the exporter in the getter method, e.g.:
public Object getCustomExporter()
{ return new MyExporter(); }Since, this getter is called in the Invoke Application phase, the exporter instance can pass any other application data in the constructor of the custom exporter, e.g.:
public Object getCustomExporter()
{ return new MyExporter(selectedItems); }