[Geotools-gt2-users] Recommended Filter Persistence Approach?

[Eric S. v. SF <es...@us...>]

Does anyone have experience with or recommendations for persisting a Filter
structure for reuse later?  For example, a user sets up a filter for events
in a specific area that occurred after a given time and had some word in the
subject/summary of the event.  The user wants to re-run this filter
frequently and not have to re-create it each time.  Users could have many
stored filters.  System administrators also want to gather metrics for the
most commonly used search fields and values across users so that we can
tailor new features to those needs.

The most straightforward way would be to store straight CQL or (more likely)
the XML representation of a filter.  This would be pretty verbose though,
and we would have to load in and parse all the stored filters in order to
generate metrics for individual search fields and values.

The other way would be to use Hibernate and map the Filter/Expressions to a
table structure.  I've done this in the past with a much more simple query
setup, but I don't think it's feasible for the complex Filter hierarchy of
the OGC standards.

Has anyone tried either approach, or come up with something completely
different?

adTHANKSvance,

e
-- 
View this message in context: http://n2.nabble.com/Recommended-Filter-Persistence-Approach-tp4655568p4655568.html
Sent from the geotools-gt2-users mailing list archive at Nabble.com.