Apache Unomi 2 also introduces a set of administrative endpoints allowing new schemas and/or schemas extensions to be registered. More details about JSON Schemas implementation are available in the corresponding migration guide for more details. 1.1.5. NEW WEB TRACKER Apache Unomi 2.0 Web Tracker, located in extensions/web-tracker/ has been completely rewritten. It is no longer based on an external library and extracted from our tracker sample which is available here: https://github.com/apache/unomi/blob/master/extensions/web- tracker/wab/src/main/webapp/index.html . However you will still need to use the REST API

API changes, the persistence API interface didn’t changed. Any custom Apache Unomi plugins or extensions should continue to work on Apache Unomi 1.5.0. The only notable changes are located at the El your own condition type implementations. For more details on building your own custom plugins/extensions, please refer to the corresponding sections. 8.22.1. EXISTING CONDITION TYPE DESCRIPTORS Here it is also possible to build your own custom condition types by developing custom Unomi plugins/extensions. You will also note that some condition types can re-use a parentCondition. This is a way to inherit

properties> } Some types can be dynamically defined at runtime by calling to the REST API while other extensions are done via Unomi plugins. Part of extending Unomi, therefore, is a matter of defining new types HTTP sessions. 1.2. EXTENDING UNOMI VIA PLUGINS Unomi is architected so that users can provided extensions in the form of plugins. 1.2.1. TYPES VS. INSTANCES Several extension points in Unomi rely on