Java Client API: Removal of Deprecated Interfaces

c.m.c.admin.ServerConfigurationManager:

Use the following equivalent methods instead.

c.m.c.admin.TransformExtensionsManager:

Overloads of the listed methods that accept a paramTypes map have been removed. Use one of the overloads that does not accept parameter metadata. This metadata is not required to install or use a transform.

c.m.c.admin.config

This package, its sub-packages, and all contained classes, interfaces, and types have been removed. This includes the QueryOptions and QueryOptionsBuilder classes. Create query options using your preferred JSON or XML libraries, read options from a file, or build options as a string. Read and write options using appropriate handles, such as DOMHandle, JacksonHandle, FileHandle, or StringHandle.

c.m.c.document.JSONDocumentManager:

Remove your usage. Language specifications are not supported for JSON. Calls to these methods were ignored in MarkLogic 8.

c.m.c.io.QueryOptionsHandle

Create query options using your preferred JSON or XML libraries, read options from a file, or build options as a string. Read and write options using appropriate handles, such as DOMHandle, JacksonHandle, FileHandle, or StringHandle. This class is no longer needed with the removal of QueryOptions and QueryOptionsBuilder.

c.m.c.query:

The key-value search capability has been removed. Build equivalent queries using a StructuredQueryDefinition (JSON property query or element query) or QBE.

c.m.c.query.QueryManager:

The key-value search capability has been removed. Build equivalent queries using a StructuredQueryDefinition (JSON property query or element query) or QBE. c.

c.m.c.io.SearchHandle.forceDOM

Remove your usage. This setting was ignored in MarkLogic 8.

c.m.c.query.StructuredQueryBuilder:

FragmentScope.DOCUMENT

Use FragmentScope.DOCUMENTS.

StructuredQueryBuilder (nested classes):

Continue to construct structured queries using StructuredQueryDefinition methods, as before. The return type from the query builder methods is always StructuredQueryDefinition now. For example, StructuredQueryDefinition.and() used to return an AndQuery, but now returns a StructuredQueryDefinition.

StructuredQueryBuilde.elementConstraint

StructuredQueryBuilder.containerConstraint