Cheers,

Andy Gibson

I have a question: How do I set a class extending the ExtendedEntityQuery in components.xml. Is that the “class” attribute? And how can i ovverride the constructor for settings lines like getOrderKeyFieldMap().put(“id”, “p.id”) in the components.xml? Thanks

Thanks for this tutorial

In theory, you could override the getEntityManager() method in the EntityQuery or the ExtendedEntityQuery I use and return the FullTextEntityManager they use in your reference. However, the style of querying is completely different so I’m not sure they share enough common code to work well.

To be honest, though, the pagination code isn’t that difficult, you could just create a full text search query which takes a class as a parameter and re-write the code for firstResult, count, first, next, last, etc in no time.

The EntityQuery objects do subclass some Query objects which you can look and see how good the hierarchy they implemented is. I don’t think it is very open to extension though. I wrote my own query hierarchy that implements the basic pagination stuff and enhanced ordering so you could get a list of results from anything (file list etc) and then extended them for JPA, Hibernate queries, and also to allow for better handling of EL expressions in restrictions.

The code isn’t that tricky, especially since the EntityQuery pretty much describes what the query needs to do.

Cheers,

Andy

How could we get the results from a Hibernate Search-based query into your dataTable that can be paginated/sorted? Could you give some pointers for me to get started down that road?

Thanks.

Personally, I’ve never really thoroughly implemented page numbers using this method as it requires a record count of the results. However, I would just add a gotoPage method on the entity query and pass in the value from the jsf page link. In the method, I would have something like :


public void gotoPage(int pageNum) {
firstResult = pageNum * pageSize;
refresh();
}


I’d add a method to get a list of page numbers, put a ui:repeat on there to access the values and use the var as a parameter to the gotoPage method in the paginator:


<ui:repeat value="#{p_queryBean.getPageList}" var="v_page">
<a:commandLink action="#{p_queryBean.gotoPage(v_page)}" value="#{v_page}"/>
</ui:repeat>


You can put this in the paginator to get re-use each time by adding the getPageList() method on the entity bean.

By using a pageList method returning a value, you can just return 1 through N, or 1 through 9 and then 15 to 19 if you have a lot of pages. You can also not render the page numbers if your pageList returns null or is empty. Also, if you change your page list strategy down the road, you can change it for all queries by implementing it in the extended entity query.

Hope this helps,

Cheers,

Andy Gibson