Loading schemas

Similar to non-REST modules, schemas are loaded by default via the App-Services server on port 8000. The Property reference defines the various properties for how a connection is made to 8000.

Specifying collections and permissions for schemas

As of version 2.6.0, schemas can be loaded from child directories of src/main/ml-schemas, and they can also be loaded into custom collections. See https://github.com/marklogic-community/ml-javaclient-util/wiki/Loading-files#specifying-collections-and-permissions for more information.

Loading TDE templates

As of version 2.7.0, TDE rulesets no longer need to have a "tdex" or "tdej" suffix. Instead, any document with a URI starting with "/tde" will be put into the "http://marklogic.com/xdmp/tde" collection.

Loading schemas into different databases

As of version 3.11.0, schemas can be loaded from database-specific paths, as defined in the Project layout page. Example:

databases
│       content-database.json
│       my-schemas-database.json
|       my-other-schemas-database.json
└───my-schemas-database
    └───schemas
            my-schema.xsd
└───my-other-schemas-database
    └───schemas
            my-other-schema.xsd

Validating TDE templates

Starting in release 3.13.0, TDE templates are validated by default. The property "mlTdeValidationEnabled" can be set to "false" to disable this behavior.

Token replacement

As of release 3.16.1, tokens will be replaced in schema files, just like they are for modules.