DECLARATIONS ARE NOW REQUIRED Scopes declarations are now required in Unomi 2. When submitting an event and specifying a scope, that scope must already be declared on the platform. Scopes can be easily object properties must be declared in a JSON schema for an event to be accepted. A new property, flattenedProperties has been introduced to the event object, this property has been added to store the properties properties. If there is dynamic properties that you want to send with your event, you should use the flattenedProperties field of the event. It’s also necessary to specify the format of the values which are

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.2.8. How to send a login event to Unomi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 8.6. Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 8.6.2. Event types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conceptually, an event can be seen as a sentence, the event’s type being the verb, the source the subject and the target the object. Event structure: { "eventType": event>, "scope": "scope": event>, "source": , "target": , "properties": } Source and target can be any Unomi item but are not limited to them. In particular, as long applications using the JSON format and a typical page view event from a web site could look something like the following: Example page view event: Apache Unomi 1.1.x - Documentation - 2 { "eventType":

ApplicationContext Internationalization using MessageSource Standard and Custom Events Annotation-based Event Listeners Asynchronous Listeners Ordering Listeners Generic Events Convenient access to low-level PlatformTransactionManager Choosing between programmatic and declarative transaction management Transaction bound event Application server-specific integration IBM WebSphere Oracle WebLogic Server Solutions to common the Beans module and adds support for internationalization (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet

ApplicationContext Internationalization using MessageSource Standard and custom events Annotation-based event listeners Asynchronous Listeners Ordering listeners Generic events Convenient access to low-level PlatformTransactionManager Choosing between programmatic and declarative transaction management Transaction bound event Application server-specific integration IBM WebSphere Oracle WebLogic Server Solutions to common the Beans module and adds support for internationalization (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet

Events .......................................................................... 145 Annotation-based Event Listeners ............................................................ 148 Asynchronous Listeners between programmatic and declarative transaction management ........ 394 17.8. Transaction bound event ................................................................................ 394 17.9. Application the Beans module and adds support for internationalization (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet

........................................................................... 152 Annotation-based event listeners ............................................................. 155 Asynchronous Listeners between programmatic and declarative transaction management ........ 402 17.8. Transaction bound event ................................................................................ 402 17.9. Application the Beans module and adds support for internationalization (using, for example, resource bundles), event propagation, resource loading, and the transparent creation of contexts by, for example, a Servlet

beans package and adds support for internationalization (I18N) (using for example resource bundles), event-propagation, resource-loading, and the transparent creation of contexts by, for example, a servlet integration with Spring's AOP features, message resource handling (for use in internationalization), event propagation, and application-layer specific contexts such as the WebApplicationContext for use in MessageSource, providing access to messages in i18n-style • Access to resources, such as URLs and files • Event propagation to beans implementing the ApplicationListener interface • Loading of multiple (hierarchical)

抽象窗口工具集 AWT (Abstract Window Toolkit) O 相关软件包 java.awt 包 提供基本 GUI 组件、视觉控制和绘图工具 API。 java.awt.event 包 提供 Java GUI 事件处理 API。 大纲 GUI 组件及布局 GUI 事件处理 Applet Swing Swing 典型组件（课后自学） 组件和容器 组件 组件（Compon 组件及布局 GUI 事件处理 Applet Swing Swing 典型组件（课后自学） Java 事件和事件处理机制 从 JDK 1.1 开始，Java 采用了一种名为“事件代理模 型”（Event Delegation Model）的事件处理机制。基本原理如下： 1. 事先定义多种事件类型 2. 约定各种 GUI 组件在与用户交互时，遇到特定操作则会触 发相应的事件，即自动创建事件类对象并提交给 典型组件（课后自学） 事件处理相关概念 事件（Event） 一个事件类型的对象，用于描述了发生什么事 情，当用户在组件上进行操作时会触发相应的事件。 事件源（Event Source） 能够产生事件的 GUI 组件对象，如按 钮、文本框等。 事件处理方法（Event Handler） 能够接收、解析和处理事件类 对象，实现与用户交互功能的方法。 事件监听器（Event Listener） 调用事件处理方法的对象。

beans package and adds support for internationalization (I18N) (using for example resource bundles), event-propagation, resource-loading, and the transparent creation of contexts by, for example, a servlet integration with Spring's AOP features, message resource handling (for use in internationalization), event propagation, and application-layer specific contexts such as the WebApplicationContext for use in MessageSource, providing access to messages in i18n-style • Access to resources, such as URLs and files • Event propagation to beans implementing the ApplicationListener interface • Loading of multiple (hierarchical)