data model, One of the key differences is the removal of open maps. The properties field in the events objects provided by unomi are now restricted by JSON schema. This means object properties must be be stored as flattened and will not create dynamic mapping contrary to the properties field of the events. Here is an example for objects that used dynamic properties for URL parameters: The following our Unomi 2 migration process will handle the data model changes for you. If you are using custom events/objects, please refer to the detailed migration guide for more details. 1.1.5. NEW WEB TRACKER

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2.4. How to search for profile events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.4. Sending events using the context servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.5. Sending events using the eventcollector servlet using property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.5.4. Secured events configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1.2. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that clients can use to share data across scopes. 1.1.2. EVENTS Users' actions are conveyed from clients to the context server using events. Of course, the required information depends on what is collected and users' interactions with the observed systems but events minimally provide a type, a scope and source and target items. Additionally, events are timestamped. Conceptually, an event can be seen as

5.4. Application Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.5.5. Test Execution Events . . . . . . . . TestContext Framework to record all application events that are published in the ApplicationContext during the execution of a single test. The recorded events can be accessed via the ApplicationEvents API API within tests. See Application Events and the @RecordApplicationEvents javadoc for an example and further details. @Commit @Commit indicates that the transaction for a transactional test method should

Boot features 20. SpringApplication Customizing SpringApplication Fluent builder API Application events and listeners Web environment Using the CommandLineRunner Application exit 21. Externalized Configuration Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually a number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent

........................................................................... 39 20.3. Application events and listeners ........................................................................ 39 20.4. Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent

SpringApplication Customizing the Banner Customizing SpringApplication Fluent builder API Application events and listeners Web environment Using the CommandLineRunner Application exit 21. Externalized Configuration Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually a number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent

........................................................................... 39 20.4. Application events and listeners ........................................................................ 39 20.5. Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent

SpringApplication Customizing the Banner Customizing SpringApplication Fluent builder API Application events and listeners Web environment Using the CommandLineRunner Application exit 21. Externalized Configuration Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually a number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent

........................................................................... 39 20.4. Application events and listeners ........................................................................ 39 20.5. Application events and listeners In addition to the usual Spring Framework events, such as ContextRefreshedEvent, a SpringApplication sends some additional application events. Some events are actually number of ways, the most common being SpringApplication.addListeners(...) method. Application events are sent in the following order, as your application runs: 1. An ApplicationStartedEvent is sent