Yeah, it's a shame such a ser/deser feature isn't available in Lucene.
My idea is to have a separate module that the Query classes can delegate to
for serialization and deserialization, handling recursion for nested query
objects, and then have modules for XML, JSON, and a pseudo-Java functiona
Thanks for the reply.
The issue I have is trying to figure out how to either translate my large
programmatically generated lucene query to a string i can set as the q
parameter (which is non-trivial, since the toString methods on lucene
queries don't necessarily produce a parseable string), or ge
Use query() to have Solr search for results. You have to pass a SolrQuery
object that describes the query, and you will get back a QueryResponse (from
the org.apache.solr.client.solrj.response package).
SolrQuery has methods that make it easy to add parameters to choose a
request handler and send p
