fix bug where order was ignored in a certain virtual subnode scenario

This commit is contained in:
hns 2001-04-06 17:49:27 +00:00
parent 8a1fcd56d0
commit 3d848fb069

View file

@ -142,7 +142,8 @@ public class Relation {
aggressiveCaching = caching != null && "aggressive".equalsIgnoreCase (caching.trim()); aggressiveCaching = caching != null && "aggressive".equalsIgnoreCase (caching.trim());
// get order property // get order property
order = props.getProperty (propname+".order"); order = props.getProperty (propname+".order");
if (order != null && order.trim().length() == 0) order = null; if (order != null && order.trim().length() == 0)
order = null;
// get group by property // get group by property
groupby = props.getProperty (propname+".groupby"); groupby = props.getProperty (propname+".groupby");
if (groupby != null && groupby.trim().length() == 0) if (groupby != null && groupby.trim().length() == 0)
@ -161,6 +162,7 @@ public class Relation {
if (subnodefilter != null) { if (subnodefilter != null) {
filter = new Relation (subnodefilter, propname+".subnoderelation", home, props); filter = new Relation (subnodefilter, propname+".subnoderelation", home, props);
filter.groupby = groupby; filter.groupby = groupby;
filter.order = order;
} }
} }
} }