anchor.diff:  }
   ----
   
  -Sometimes, we want to work with process scoped beans, in the absence of an association with a process instance, for example before starting a process. If no process instance is currently active, instances of BusinessProcessScoped beans are temporarily stored in a local scope (I.e. the Conversation or the Request, depending on the context. If this scope is later associated with a business process instance, the bean instances are flushed to the process instance.
  +Sometimes, we want to work with process scoped beans, in the absence of an association with a process instance, for example before starting a process. If no process instance is currently active, instances of +BusinessProcessScoped+ beans are temporarily stored in a local scope, i.e. the +Conversation+ or the +Request+, depending on the context. If this scope is later associated with a business process instance, the bean instances are flushed to the process instance.
   
   ==== Injecting Process Variables
   
   Process variables are available for injection. flowable-cdi supports 
  -	  	
  + 	
   * type-safe injection of +@BusinessProcessScoped+ beans using +@Inject \[additional qualifiers\] Type fieldName+
   * unsafe injection of other process variables using the +@ProcessVariable(name?)+ qualifier: 
   
  
positive.code: 
  ==== Configuring the Process Engine
  
  Configuration depends on the selected ProcessEngineLookup-Strategy (cf. previous section). Here, we focus on the configuration options available in combination with the LocalProcessEngineLookup, which requires us to provide  a Spring flowable.cfg.xml file on the classpath.
  
  Flowable offers different ProcessEngineConfiguration implementations mostly dependent on the underlying transaction management strategy. The flowable-cdi module is not concerned with transactions, which means that potentially any transaction management strategy  can be used (even the Spring transaction abstraction). As a convenience, the cdi-module provides two custom ProcessEngineConfiguration implementations: 
       	
  * ++org.flowable.cdi.CdiJtaProcessEngineConfiguration++: a subclass of the Flowable JtaProcessEngineConfiguration,  can be used if JTA-managed transactions should be used for Flowable
  * ++org.flowable.cdi.CdiStandaloneProcessEngineConfiguration++: a subclass of the Flowable StandaloneProcessEngineConfiguration,  can be used if plain JDBC transactions should be used for Flowable. The following is an example flowable.cfg.xml file for JBoss 7:
       
  [source,xml,linenums]
  ----
  <?xml version="1.0" encoding="UTF-8"?>
  
negative.code: == CDI integration
  
  The flowable-cdi modules leverages both the configurability of Flowable and the extensibility of cdi. The most prominent features of flowable-cdi are:
  
  * Support for @BusinessProcessScoped beans (CDI beans whose lifecycle is bound to a process instance),
  * A custom El-Resolver for resolving CDI beans (including EJBs) from the process,
  * Declarative control over a process instance using annotations,
  * Flowable is hooked-up to the CDI event bus,
  * Works with both Java EE and Java SE, works with Spring,
  * Support for unit testing.
  
  