Ordering.orderList generates a "set operation not supported" exception when
executed on a query with a specific pageSize.
I understand how this bug could come about, and I'm guessing that I need to
manually forcing each fault to resolve before calling orderList.
However, I suspect this should be handled by the framework rather than the
user.
-Mike
=============code==============
aSelectQuery.addOrderings(currentSortOrder);
aSelectQuery.setFetchLimit(recordFetchLimit.intValue());
aSelectQuery.setPageSize(batchSize);
reportRowsList = dataContext.performQuery(aSelectQuery);
[...]
Ordering.orderList(reportRowsList, currentSortOrder);
=============code==============
=============error=============
java.lang.UnsupportedOperationException: set operation not supported
at
org.objectstyle.cayenne.access.IncrementalFaultList$IncrementalListIterator.set(IncrementalFaultList.java:915)
at java.util.Collections.sort(Collections.java:159)
at org.objectstyle.cayenne.query.Ordering.orderList(Ordering.java:97)
at
com.gvea.struts.utils.ReportComponent.sortByColumn(ReportComponent.java:1286)
=============error=============
This archive was generated by hypermail 2.0.0 : Wed Jan 14 2004 - 12:59:12 EST