月满闲庭的博客

2.18.2 配置和设置(Configuration and setup)If an event-listener is configured in the process engine configuration, it will be active when the process engine starts and will remain active after subsequent reboots of the engine.The property eventListeners expect

2.18.4 向流程定义增加侦听器It’s possible to add listeners to a specific process-definition. The listeners will only be called for events related to the process definition and to all events related to process instances that are started with that specific process def

2.18.5 通过API分发事件We opened up the event-dispatching mechanism through the API, to allow you to dispatch custom events to any listeners that are registered in the engine. It’s recommended (although not enforced) to only dispatch FlowableEvents with type CUS

2.18 事件处理器（Event handlers）The event mechanism in the Flowable engine allows you to get notified when various events occur within the engine. Take a look at all supported event types for an overview of the events available.It’s possible to register a list

2.17 映射诊断上下文（Mapped Diagnostic Contexts）Flowable supports the Mapped Diagnostic Contexts feature of SLF4j. This basic information is passed to the underlying logger along with what is going to be logged:processDefinition Id as mdcProcessDefinitionIDpro

2.16 日志All logging (flowable, spring, mybatis, …) is routed through SLF4J and allows for selecting the logging-implementation of your choice.所有日志记录（flowable、spring、mybatis等）都通过SLF4J路由，允许您选择自己的日志实现（logging-implementation）。By default no SFL4J-binding JAR

2.11 邮件服务器配置Configuring a mail server is optional. Flowable supports sending e-mails in business processes. To actually send an e-mail, a valid SMTP mail server configuration is required. See the e-mail task for the configuration options.配置邮件服务器是可选的。Flow

2.9 作业执行器（Job Executor）（从6.0.0版起）The async executor of Flowable v5 is the only available job executor in Flowable V6, as it is a more performant and more database friendly way of executing asynchronous jobs in the Flowable engine. The old job executor of

2.7 数据库表名说明The database names of Flowable all start with ACT_. The second part is a two-character identification of the use case of the table. This use case will also roughly match the service API.Flowable的数据库表名称都以ACT_开头。第二部分是数据库表用例的双字符标识。这个用例也将大致与服务API（

2.5 支持的数据库Listed below are the types (case sensitive!) that Flowable uses to refer to databases.下面列出的是Flowable用于引用数据库的数据库类型（区分大小写！）。数据库类型JDBC URL举例备注h2jdbc:h2:tcp://localhost/flowable缺省配置数据库mysqljdbc:mysql://localhost:3306/flowable?auto

2.4 JNDI数据源配置By default, the database configuration for Flowable is contained within the db.properties files in the WEB-INF/classes of each web application. This isn’t always ideal because it requires users to either modify the db.properties in the Flowab

2.3 数据库配置There are two ways to configure the database that the Flowable engine will use. The first option is to define the JDBC properties of the database:jdbcUrl: JDBC URL of the database.jdbcDriver: implementation of the driver for the specific datab

《Flowable 6.6.0 BPMN用户指南》2. 配置2.1 创建ProcessEngine2.2 ProcessEngineConfiguration Bean2.3 数据库配置2.4 JNDI数据源配置2.5 支持的数据库/2.6 创建数据库表2.7 数据库表名说明 / 2.8 数据库升级2.9 作业执行器/2.10 作业执行器激活2.11 ~ 2.152.16 日志2.17 映射诊断上下文2.18 事件处理器（Event handlers）2.18.2 配置和设置/2.

2.2 ProcessEngineConfiguration BeanThe flowable.cfg.xml must contain a bean that has the id ‘processEngineConfiguration’.flowable.cfg.xml文件必须包含一个id为“processEngineConfiguration”的bean。<bean id="processEngineConfiguration" class="org.flowable.engine.imp

《Flowable 6.6.0 BPMN用户指南》2 配置2.1 创建ProcessEngineThe Flowable process engine is configured through an XML file called flowable.cfg.xml. Note that this is not applicable if you’re using the Spring style of building a process engine.The easiest way to obt