Should we make a new "SearchCriteria" object that looks similar to our PageCriteria object?
Should search information be folded into the PageCriteria object?
How do we make the PageCriteria object flexible enough to support the kinds of queries we need to do
Criteria data structure
What should the SearchCriteria object look like?
Option 1: Hibernate criteria API
(How) do we reconstruct the URL query from the hibernate criteria-like data structure?
Option 2: URL query syntax
Who is responsible for translation from this data structure to Hibernate? Right now, logical place seems like StandardQueryCriteriaBuilder, but that does not currently know about specific model data structure.
General
What kinds of queries do we need to support?
AND/OR syntax in URLs
What do the SQL queries look like?
Ideas
Servlet code is responsible for choosing "key" names (that is, table names) to query on.
Servlet code uses facilities provided by PageCriteria to specify the "type" of query.
PageCriteria will be named something more general.