DmnEngineConfiguration.createStandaloneDmnEngineConfiguration() ĭmnEngineConfiguration.createStandaloneInMemDmnEngineConfiguration() Īll these DmnEngineConfiguration.createXXX() methods return a DmnEngineConfiguration that can be further tweaked if needed. It is also possible to not use a configuration file and create a configuration based onĭefaults (see the different supported classes for more information). DmnEngineConfiguration.ĬreateDmnEngineConfigurationFromResourceDefault() ĬreateDmnEngineConfigurationFromResource(String resource) ĬreateDmnEngineConfigurationFromResource(String resource, String beanName) ĬreateDmnEngineConfigurationFromInputStream(InputStream inputStream) ĬreateDmnEngineConfigurationFromInputStream(InputStream inputStream, String beanName) It is also possible to use a different bean ID (for example, see line 3). The DMNEngineConfiguration object can also be created programmatically using the configuration file. This does not mean that Flowable DMN can only be used in a Spring environment! We are simply leveraging the parsing and dependency injection capabilities of Spring internally for building up the engine. Note that the configuration XML is in fact a Spring configuration. The following sections will give a detailed overview of the configuration properties. The following snippet shows an example configuration. This will look for a file on the classpath and construct an engine based on the configuration in that file. The easiest way to obtain a DmnEngine, is to use the .DmnEngines class: DmnEngine dmnEngine = DMNEngines.getDefaultDmnEngine() Note that this is not applicable if you’re using the Spring style of building a DMN engine. The Flowable DMN engine is configured through an XML file named. As a result, parts of the documentation are very similar to their process engine counterpart. The Flowable DMN engine is structured in a very similar way to the Flowable process engine.
0 kommentar(er)
