Author: buildbot
Date: Tue Jul 23 13:48:09 2013
New Revision: 870778
Log:
Production update by buildbot for cxf
Modified:
websites/production/cxf/content/cache/docs.pageCache
websites/production/cxf/content/docs/jax-rs-search.html
Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/cxf/content/docs/jax-rs-search.html
==============================================================================
--- websites/production/cxf/content/docs/jax-rs-search.html (original)
+++ websites/production/cxf/content/docs/jax-rs-search.html Tue Jul 23 13:48:09
2013
@@ -171,6 +171,8 @@ An expression such as "name==CXF*" can b
<p>The last two operators, ","(OR) and ";"(AND) are used to concatenate and
build composite (possibly nested) expressions, while the first 6 operators are
used to build so called primitive expressions. </p>
+<p>From CXF 2.7.7: single '=' operator can be optionally supported instead of
'==': set a "fiql.support.single.equals.operator" contextual property to
"true". </p>
+
<p>As you can see FIQL is rich enough for the service implementations to offer
a more interesting search experience around the well-known data, while still
keeping the complexity of URI expressions under control which makes it simpler
to share such URI queries as well as use the same query language no matter what
data store is used internally by the service. </p>
<p>Note, when passing the FIQL queries via URI query parameters, either
'_search' or '_s' query parameter has to be used to mark a FIQL expression for
it not to 'interfere' with other optional query parameters. Starting from CXF
2.7.2 it is also possible to use the whole query component to convey a FIQL
expression, example,</p>
