Apache Unomi 1.x - Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 11.2.3. Runtime commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . set of actions and action types (aka action descriptors) purely from Groovy scripts defined at runtime. Initially submitted to Unomi through a purpose-built REST API endpoint, Groovy actions are then an exception, it will be logged and the execution sequence will continue unless in the case of a Runtime exception (such as a NullPointerException). Action use Action types that are implemented as Java0 码力 | 158 页 | 3.65 MB | 1 年前3- Apache Unomi 2.x - Documentationset of actions and action types (aka action descriptors) purely from Groovy scripts defined at runtime. Initially submitted to Unomi through a purpose-built REST API endpoint, Groovy actions are then (https://github.com/apache/unomi/tree/master/tools/shell-commands/src/main/resources/requestBody/2.0.0) At runtime, and when starting the migration, Unomi 2.0 will take its own scripts, any additional scripts located an exception, it will be logged and the execution sequence will continue unless in the case of a Runtime exception (such as a NullPointerException). Action use Action types that are implemented as Java0 码力 | 117 页 | 4.78 MB | 1 年前3
- Apache Unomi 1.1.x - Documentation
- , "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 defines a prototype for what the actual items will be once parameterized with values known only at runtime. This is similar to the concept of classes in object-oriented programming: types define classes classes, providing the expected structure and which fields are expected to be provided at runtime, that are then instantiated when needed with actual values. 1.2.2. PLUGIN STRUCTURE Being built on top of 0 码力 | 32 页 | 477.20 KB | 1 年前3 - , "properties":
共 3 条
- 1