primefaces dataTable filterBy不调用加载方法

我正在将PrimeFaces3升级到8。3中已经工作的datatable筛选器在8中开始无法正常工作。在输入现有值以筛选不返回数据时，似乎不会触发load方法。 但是，排序列正在触发加载方法

我将datatable的惰性示例与primefaces showcase中的工作示例进行了比较，它已经是相同的了。检查日志，检查页面是否有错误，但找不到任何内容

为什么它不起作用？如何调试它

<ui:define name="content">
    <h:form id="logsform">

        <p:panel>

            <p:dataTable id="tbl" var="log"
                value="#{logBean.operationLogDataModel}" lazy="true" rows="10"
                paginator="true"  emptyMessage="#{messages['common.datatable.emptymessage']}">

                 <p:column sortBy="#{log.custNo}" filterBy="#{log.custNo}">
                    <f:facet name="header">
                        <h:outputText value="CustNo" />
                    </f:facet>
                    <h:outputText value="#{log.custNo}" />
                 </p:column>

            </p:dataTable>
        </p:panel>
    </h:form>

我的logBean可能是：

@ViewScoped
@FacesConfig(version = FacesConfig.Version.JSF_2_3)
@Named("logBean")
public class LogBean implements Serializable {

    @Inject
    @ManagedProperty("#{logBo}")
    private LogBo logBo;

    OperationLogDataModel operationLogDataModel;

    AuthUser authUser = (AuthUser) SecurityContextHolder.getContext().getAuthentication();

    public LogBean() {
    }

    @PostConstruct
    public void initModel() {
        operationLogDataModel = new OperationLogDataModel(logBo, authUser);
        documentLogList = new ArrayList<DocumentLog>();
    }

    .
    .
}

我的lazyDataModel如下所示：

public class OperationLogDataModel extends LazyDataModel<OperationLogs> {

    private static final Logger LOG = Logger.getLogger(OperationLogDataModel.class);

    private LogBo logBo;

    private String currentSortField;
    private SortOrder currentSortOrder;
    private Map<String, FilterMeta> currentFilters;

    AuthUser authUser;

    private Date startDate;
    private Date finishDate;

    public OperationLogDataModel() {
    }

    public OperationLogDataModel(LogBo logBo, AuthUser authUser) {
        this.authUser = authUser;
        this.logBo = logBo;
        super.setPageSize(Configurations.PAGE_SIZE);
    }

    public OperationLogDataModel(LogBo logBo, AuthUser authUser, Date startDate, Date finishDate) {
        this.logBo = logBo;
        this.authUser = authUser;
        super.setPageSize(Configurations.PAGE_SIZE);
        this.startDate = startDate;
        this.finishDate = finishDate;
    }

    @Override
    public List<OperationLogs> load(int first, int pageSize, String sortField, SortOrder sortOrder, Map<String, FilterMeta> filters) {
        currentSortField = sortField;
        currentSortOrder = sortOrder;
        currentFilters = filters;

        if (sortField == null) {
            sortField = "createTime";
            sortOrder = SortOrder.DESCENDING;
        }

        Criterion sqlRestriction = Restrictions.sqlRestriction("1=1");
        if (startDate != null)
            sqlRestriction = Restrictions.and(sqlRestriction, Restrictions.ge("createTime", startDate));
        if (finishDate != null)
            sqlRestriction = Restrictions.and(sqlRestriction, Restrictions.le("createTime", finishDate));

        List<OperationLogs> logs = new ArrayList<OperationLogs>();
        try {
            if (authUser.getAuthorityName().equals(Role.ROLE_ORDINARY.getName()))
                sqlRestriction = Restrictions.and(sqlRestriction, Restrictions.eq("username", authUser.getName()));

            super.setRowCount(logBo.countLogs(-1, -1, null, sortOrder.name(), filters, null, sqlRestriction).intValue());


            System.out.println("load called!");


            logs = logBo.listLogs(first, pageSize, sortField, sortOrder.name(), filters, null, sqlRestriction);

        } catch (Exception e) {
            LOG.error(e, e);
        }

        return logs;
    }

    @Override
    public String getRowKey(OperationLogs logs) {
        return logs.getId() + "";
    }

    @Override
    public OperationLogs getRowData(String rowKey) {
        try {
            return logBo.getLogById(Long.parseLong(rowKey));
        } catch (Exception e) {
            return null;
        }
    }

    @Override
    public void setPageSize(int pageSize) {
        super.setPageSize(pageSize);
    }

    public void onFilter(AjaxBehaviorEvent event) {
    }

    public String getCurrentSortField() {
        return currentSortField;
    }

    public void setCurrentSortField(String currentSortField) {
        this.currentSortField = currentSortField;
    }

    public SortOrder getCurrentSortOrder() {
        return currentSortOrder;
    }

    public void setCurrentSortOrder(SortOrder currentSortOrder) {
        this.currentSortOrder = currentSortOrder;
    }

    public Map<String, FilterMeta> getCurrentFilters() {
        return currentFilters;
    }

    public void setCurrentFilters(Map<String, FilterMeta> currentFilters) {
        this.currentFilters = currentFilters;
    }
}

上面加载方法中的logBo.listLogs只是调用下面的findEntities方法。但我不认为执行会到达这里，因为在过滤时，尽管调用了上面的load方法并在排序中正常工作，但从未调用过它。我这么认为是因为printly在logBo.listLogs之前

@Override
public List<T> findEntities(int first, int pageSize, String sortField,
        String sortOrder, Map<String, FilterMeta> filters,
        Map<String, String> aliases, Criterion extraCriterion)
        throws SecurityException, NoSuchFieldException {
    Criteria crit = sessionFactory.getCurrentSession().createCriteria(
            getPersistentClass());

    crit = prepareCriteria(first, pageSize, sortField, sortOrder, filters,
            aliases, extraCriterion, crit);

    crit.setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);
    return crit.list();
}

private Criteria prepareCriteria(int first, int pageSize, String sortField,
        String sortOrder, Map<String, FilterMeta> filters,
        Map<String, String> aliases, Criterion extraCriterion, Criteria crit)
        throws NoSuchFieldException {
    if (aliases != null && !aliases.isEmpty()) {
        Iterator<Entry<String, String>> iterator = aliases.entrySet()
                .iterator();
        while (iterator.hasNext()) {
            Entry<String, String> entry = iterator.next();
            crit.createAlias(entry.getKey(), entry.getValue(),
                    Criteria.LEFT_JOIN);
        }
    }

    if (extraCriterion != null) {
        crit.add(extraCriterion);
    }

    if (sortField != null && !sortField.isEmpty()) {
        if (!sortOrder.equalsIgnoreCase("UNSORTED")) {
            if (sortOrder.equalsIgnoreCase("ASCENDING")) {
                crit = crit.addOrder(Order.asc(sortField));
            } else {
                crit = crit.addOrder(Order.desc(sortField));
            }
        }
    }

    if (filters != null && !filters.isEmpty()) {
        Iterator<Entry<String, FilterMeta>> iterator = filters.entrySet()
                .iterator();
        while (iterator.hasNext()) {
            Entry<String, FilterMeta> entry = iterator.next();
            Class<?> type = getPersistentClass().getDeclaredField(
                    entry.getKey()).getType();
            try {
                if (type.isEnum() || Number.class.isAssignableFrom(type)
                        || Double.class.isAssignableFrom(type)) {
                    crit = crit.add(Restrictions.eq(entry.getKey(), type
                            .getDeclaredMethod("valueOf", String.class)
                            .invoke(null, entry.getValue())));
                } else {
                    crit = crit.add(Restrictions.like(entry.getKey(),
                            String.valueOf(entry.getValue().getFilterValue()), MatchMode.START));
                }
            } catch (Exception ex) {
            }
        }
    }

    if (first != -1) {
        crit = crit.setFirstResult(first);
    }

    if (pageSize != -1) {
        crit = crit.setMaxResults(pageSize);
    }
    return crit;
}

---

PS更新：似乎我弄错了，在筛选过程中调用了load。可能我需要检查我的自定义通用筛选代码。

我发现，一旦我在一个filterBy字段的列中输入了一些值，我故意留空的其他列filterBy字段将作为以下内容进入自定义查询：

CriteriaImplcom.xxx.model.OperationLogs:this[][1=1，custNo像11111%，refNo像null%，username像null%]

因此，在生成查询时添加控件：

 if(entry.getValue().getFilterValue() == null) {
    continue;
 }

紧接着：

if (filters != null && !filters.isEmpty()) {
    Iterator<Entry<String, FilterMeta>> iterator = filters.entrySet()
            .iterator();
    while (iterator.hasNext()) {

解决了这个问题

我正在进行全面升级，包括Primefaces、JSF、Spring、Hibernate等

---

我想我在hibernate升级中遗漏了一些东西，因为它在以前的版本中成功运行。

您检查了吗？您收到的是空消息，因此负载似乎被调用。你怎么做过滤器部分？因为PF>5过滤器值是一个对象而不是StringYes，所以我是根据迁移指南进行升级的。但我可能错过了一些东西。添加了加载方法签名。顺便说一句，我确信在filterBy上不会调用load，而在通过检查日志进行排序时会调用load。您是否尝试过使用普通页面，不使用组合和任何其他组件作为一个组件？你能发布你的logBean定义和你所有的懒豆吗？添加了logBean和lazyModel。我会尽快试用普通版，并通知您。谢谢更新：似乎我弄错了，在筛选过程中调用了加载。可能，我需要检查我的自定义通用筛选代码。