org.geotools.catalog
Class QueryRequest

java.lang.Object
  org.geotools.catalog.QueryRequest

public class QueryRequest

extends java.lang.Object

Represents a query against metadata.

This class represents a strong extention of the existing geotools Filter and Expression construct. I have chosen the name Query to agree with the origional meaning of the data.Query which represented a metadata query matching the metadata typeName and a Feature Filter on the resulting FeatureCollection.

Another way of thinking about this is that it offers a walk of the Expr construct from the persepective of Metadata. I noticed that although Expression and Filter are defined as interfaces I have only ever seen one implementation. The *magic* of data specific behaviour seems to occur only when walking the tree, rather than implementing a custom FilterFactory (& thus custom tree mnodes).

So this class provides a tree construct for a QueryWalker to navigate through, I am folloing the direct example of Filter and Expression here (even though I think there may be a better way).

Q: Should this class turn itself into a data.Query? Or should I turn data.Query into a subclass.

Version:

2.1

Author:

Jody Garnett, Refractions Research

Field Summary

static QueryRequest

ALL

Constructor Summary

QueryRequest(Filter expr)

Method Summary

boolean	match(java.lang.Object bean)
protected boolean	matchBean(java.lang.Object bean)
protected boolean	matchMetadata(org.opengis.catalog.MetadataEntity meta)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

ALL

public static QueryRequest ALL

Constructor Detail

QueryRequest

public QueryRequest(Filter expr)

Method Detail

match

public boolean match(java.lang.Object bean)

matchBean

protected boolean matchBean(java.lang.Object bean)

matchMetadata

protected boolean matchMetadata(org.opengis.catalog.MetadataEntity meta)