Hi gentlefolks,
We are developing FT search via xPlore/DFS and had stumble upon next issue.
We need to pass two type of locations: excluded and included.
Those locations are passed to setScopes method of StructuredQuery instance.
What is happening during call to SearchService execute.
1) Excluded folder do not exists at DMS side – all works well, search results are returned;
I believe in this case DFC performs some sort of validation.
2) Excluded folder exists – exception is thrown:
>>>
Excluded folder locations are not supported by xPlore.; ERRORCODE: ff; NEXT: null
at com.documentum.fc.client.search.impl.generation.docbase.xquery.LocationScopeGenerator.computeTypeOfConstraints(LocationScopeGenerator.java:236)
at com.documentum.fc.client.search.impl.generation.docbase.xquery.LocationScopeGenerator.<init>(LocationScopeGenerator.java:47)
at com.documentum.fc.client.search.impl.generation.docbase.xquery.XQueryGenerator.getQueryStatement(XQueryGenerator.java:71)
>>>
With pure-database search all works as a charm (but this is not an option for us).
There seems to be no actual requests to xPlore as this happens on DFC API level.
Behavior is the same for 6.7.x and 7.1.x DFS libs.
xPlore version used is 1.4.
While it is obvious that this happens by design I wonder about the following:
1) Can anyone tell if there are plans to change this in any DFS/xPlore release?
2) Is this limitation really caused by xPlore design? Should we try 1.5 also?
3) Maybe direct xPlore API/XQuery can help here?
Thanks in advance for any suggestion or comment.
