### Drools 5.0 CR1 New and Noteworthy Release Summary

Previous New and Noteworth release summary notes:
M1
M2
M3/M4
M5

## Drools Guvnor

Guvnor of course has some fixes on usability, security and bugs. But the biggest new thing is that Guvnor can now be translated. Default language is English and currently you can also use Spanish. Date formats and default languages can be set with drools.dateformat, drools.defaultlanguage and drools.defaultcountry in preferences.properties file. These properties are then used when Guvnor builds packages.

## Drools Flow

JPA

Firstly, we have improved our support for persistence (JPA) and transactions (JTA). An example on how to use persistence and transactions in combination with processes:

// create a new JPA-based session and specify the JPA entity manager factoryEnvironment env = KnowledgeBaseFactory.newEnvironment();env.set( EnvironmentName.ENTITY_MANAGER_FACTORY, Persistence.createEntityManagerFactory( "emf-name" ) );env.set( EnvironmentName.TRANSACTION_MANAGER, TransactionManagerServices.getTransactionManager() );        StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession( kbase, null, env ); // KnowledgeSessionConfiguration may be null, and a default will be usedint sessionId = ksession.getId();// if no transaction boundary is specified, the method invocation is executed in a new transaction automaticallyProcessInstance processInstance = ksession.startProcess( "org.drools.test.TestProcess" );// the users can also specify the transaction boundary themselvesUserTransaction ut = (UserTransaction) new InitialContext().lookup( "java:comp/UserTransaction" );ut.begin();ksession.insert( new Person( "John Doe" ) );ksession.startProcess( "org.drools.test.TestProcess" );ksession.fireAllRules();ut.commit();

Variable Injection

Secondly, we now support direct access to process variables in both MVEL and Java in code constraints and actions, so if you have a variable called “person” in your process, you can now describe constraints like:

• [Java code constraint] return person.getAge() > 20;
• [MVEL action] System.out.println(person.name);

## Eclipse plugin

Some minor bug fixes were added related to the Eclipse plugin:

• The audit log now also supports the old Drools4 format.
• Drools runtimes now support the directory structure of the binary download.
• Fixed a template to create a new RuleFlow process
• Issue with changes to an action node not being detected fixed

## Drools Core and Fusion

Type safe configuration

In addition to the ability of configuring options in drools through configuration files, system properties and by setting properties through the API setProperty() method, Drools-API now supports type safe configuration.

We didn’t want to add specific methods for each possible configuration methods for two reasons: it polutes the API and every time a new option is added to Drools, the API would have to change. This way, we followed a modular, class based configuration, where a new Option class is added to the API for each possible configuration, keeping the API stable, but flexible at the same time.

So, in order to set configuration options now, you just need to use the enumerations or factories provided for each option. For instance, if you want to configure the knowledge base for assert behavior “equality” and to automatically remove identities from pattern matchings, you would just use the enums:

KnowledgeBaseConfiguration config = KnowledgeBaseFactory.newKnowledgeBaseConfiguration();config.setOption( AssertBehaviorOption.EQUALITY );config.setOption( RemoveIdentitiesOption.YES );

For options that don’t have a predefined constant or can assume multiple values, a factory method is provided. For instance, to configure the alpha threshold to 5, just use the “get” factory method:

config.setOption( AlphaThresholdOption.get(5) );

As you can see, the same setOption() method is used for the different possible configurations, but they are still type safe. The following test cases show examples on how to configure KnowledgeBuilder options and KnowledgeBase options:

New accumulate functions: collectSet and collectList

There are times when it is necessary to collect sets or lists of values that are derived from the facts attributes, but are not facts themselves. In such cases, it was not possible to use the collect CE. So, Drools now has two accumulate functions for such cases: collectSet for collecting sets of values (i.e., with no duplicate values) and collectList for collecting lists of values (i.e., allowing duplicate values):

# collect the set of unique names in the working memory$names : Set() from accumulate( Person($n : name, $s : surname ), collectSet($n + " " + $s ) )# collect the list of alarm codes from the alarms in the working memory$codes : List() from accumulate( Alarm( $c : code,$s : severity ),                         collectList( $c +$s ) )

New metadata for type declarations: @propertyChangeSupport

Facts that implement support for property changes as defined in the Javabean(tm) spec, now can be annotated so that the engine register itself to listen for changes on fact properties. The boolean parameter that was used in the insert() method in the Drools 4 API is deprecated and does not exist in the drools-api module.

declare Person@propertyChangeSupportend

Batch Executor
No sooner had we introduced the parameters api in M3 than we have killed them off in favour of the new BatchExecutor interface and Command api. Batch Executor allows for the scripting of of a Knowledge session using Commands, which can also re, both the StatelessKnowledgeSession and StatefulKnowledgeSession implement this interface

Commands are created using the CommandFactory and executed using the “execute” method, such as the following insert Command:

ksession.execute( CommandFactory.newInsert( person ) );

Typically though you will want to execute a batch of commands, this can be achieved via the composite Command BatchExecution. BatchExecutionResults is now used to handle the results, some commands can specify “out” identifiers which it used to add the result to the BatchExecutionResult. Handily querries can now be executed and results added to the BatchExecutionResult. Further to this results are scoped to this execute call and return via the BatchExecutionResults:

List<Command> cmds = new ArrayList<Command>();cmds.add( CommandFactory.newSetGlobal( "list1", new ArrayList(), true ) );cmds.add( CommandFactory.newInsert( new Person( "jon", 102 ), "person" ) );cmds.add( CommandFactory.newQuery( "Get People" "getPeople" );BatchExecutionResults results = ksession.execute( CommandFactory.newBatchExecution( cmds ) );results.getValue( "list1" ); // returns the ArrayListresults.getValue( "person" ); // returns the inserted fact Personresults.getValue( "Get People" );// returns the query as a QueryResults instance.

The CommandFactory details the supported commands, all of which can marshalled using XStream and the BatchExecutionHelper. This can be combined with the pipeline to automate the scripting of a session.

Action executeResultHandler = PipelineFactory.newExecuteResultHandler();Action assignResult = PipelineFactory.newAssignObjectAsResult();assignResult.setReceiver( executeResultHandler );Transformer outTransformer = PipelineFactory.newXStreamToXmlTransformer( BatchExecutionHelper.newXStreamMarshaller() );outTransformer.setReceiver( assignResult );KnowledgeRuntimeCommand batchExecution = PipelineFactory.newBatchExecutor();batchExecution.setReceiver( outTransformer );Transformer inTransformer = PipelineFactory.newXStreamFromXmlTransformer( BatchExecutionHelper.newXStreamMarshaller() );inTransformer.setReceiver( batchExecution );Pipeline pipeline = PipelineFactory.newStatelessKnowledgeSessionPipeline( ksession );pipeline.setReceiver( inTransformer );

Using the above for a rulset that updates the price of a Cheese fact, given the following xml to insert a Cheese instance using an out-identifier:

<batch-execution><insert out-identifier='outStilton'>  <org.drools.Cheese>    <type>stilton</type>    <price>25</price>    <oldPrice>0</oldPrice>  </org.drools.Cheese></insert></batch-execution>

We then get the following BatchExecutionResults:

<batch-execution-results> <result identifier='outStilton'>   <org.drools.Cheese>     <type>stilton</type>     <oldPrice>0</oldPrice>            <price>30</price>   </org.drools.Cheese> </result></batch-execution-results>

The following unit test XStreamBatchExecutionTest shows in much more detail how to use all the other commands, such as querries, and what the xml looks like. BatchExecutionHelper also documents the xml.

Marshalling

The MarshallerFactory is used to marshal and unmarshal StatefulKnowledgeSessions. At the simplest it can be used as follows:

// ksession is the StatefulKnowledgeSession// kbase is the KnowledgeBaseByteArrayOutputStream baos = new ByteArrayOutputStream();Marshaller marshaller = MarshallerFactory.newMarshaller( kbase );marshaller.marshall( baos, ksession );baos.close();

However with marshalling you need more flexibility when dealing with referenced user data. To achieve this we have the ObjectMarshallingStrategy interface. Two implementations are provided, but the user can implement their own. The two supplied are IdentityMarshallingStrategy and SerializeMarshallingStrategy. SerializeMarshallingStrategy is the default, as used in the example above and it just calls the Serializable or Externalizable methods on a user instance. IdentityMarshallingStrategy instead creates an int id for each user object and stores them in a Map the id is written to the stream. When unmarshalling it simply looks to the IdentityMarshallingStrategy map to retrieve the instance. This means that if you use the IdentityMarshallingStrategy it’s stateful for the life of the Marshaller instance and will create ids and keep references to all objects that it attempts to marshal. Here is he code to use a IdentityMarshallingStrategy.

ByteArrayOutputStream baos = new ByteArrayOutputStream();Marshaller marshaller = MarshallerFactory.newMarshaller( kbase, new ObjectMarshallingStrategy[] { MarshallerFactory.newIdentityMarshallingStrategy() } );marshaller.marshall( baos, ksession );baos.close();

For added flexability we can’t assume that a single strategy is suitable for this we have added the ObjectMarshallingStrategyAcceptor interface that each ObjectMarshallingStrategy has. The Marshaller has a chain of strategies and when it attempts to read or write a user object it iterates the strategies asking if they accept responsability for marshalling the user object. One one implementation is provided the ClassFilterAcceptor. This allows strings and wild cards to be used to match class names. The default is “*.*”, so in the above the IdentityMarshallingStrategy is used which has a default “*.*” acceptor.

But lets say we want to serialise all classes except for one given package, where we will use identity lookup, we could do the following:

ByteArrayOutputStream baos = new ByteArrayOutputStream();ObjectMarshallingStrategyAcceptor identityAceceptor = MarshallerFactory.newClassFilterAcceptor( new String[] { "org.domain.pkg1.*" } );ObjectMarshallingStrategy identityStratetgy = MarshallerFactory.newIdentityMarshallingStrategy( identityAceceptor );Marshaller marshaller = MarshallerFactory.newMarshaller( kbase, new ObjectMarshallingStrategy[] { identityStratetgy, MarshallerFactory.newSerializeMarshallingStrategy() } );marshaller.marshall( baos, ksession );baos.close();

Knowledge Agent

The KnowlegeAgent is created by the KnowlegeAgentFactory. The KnowlegeAgent provides automatic loading, caching and re-loading, of resources and is configured from a properties files. The KnowledgeAgent can update or rebuild this KnowlegeBase as the resources it uses are changed. The strategy for this is determined by the configuration given to the factory, but it is typically pull based using regular polling. We hope to add push based updates and rebuilds in future versions.

The Following example constructs an agent that will build a new KnowledgeBase from the files specified in the path String. It will poll those files every 30 seconds to see if they are updated. If new files are found it will construct a new KnowledgeBase, instead of updating the existing one, due to the “newInstance” set to “true” (however currently only the value of “true” is supported and is hard coded into the engine):

// Set the interval on the ResourceChangeScannerService if you are to use it and default of 60s is not desirable.ResourceChangeScannerConfiguration sconf = ResourceFactory.getResourceChangeScannerService().newResourceChangeScannerConfiguration();sconf.setProperty( "drools.resource.scanner.interval",                  "30" ); // set the disk scanning interval to 30s, default is 60sResourceFactory.getResourceChangeScannerService().configure( sconf );KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();KnowledgeAgentConfiguration aconf = KnowledgeAgentFactory.newKnowledgeAgentConfiguration();aconf.setProperty( "drools.agent.scanDirectories",                  "true" ); // we want to scan directories, not just files, turning this on turns on file scanningaconf.setProperty( "drools.agent.newInstance",                  "true" ); // resource changes results in a new instance of the KnowledgeBase being built,                            // this cannot currently be set to false for incremental building    KnowledgeAgent kagent = KnowledgeAgentFactory.newKnowledgeAgent( "test agent", // the name of the agent                                                                kbase, // the KnowledgeBase to use, the Agent will also monitor any exist knowledge definitions                                                                aconf );kagent.applyChangeSet( ResourceFactory.newUrlResource( url ) ); // resource to the change-set xml for the resources to add

KnowledgeAgents can take a empty KnowledgeBase or a populated one. If a populated KnowledgeBase is provided, the KnowledgeAgent will iterate KnowledgeBase and subscribe to the Resource that it finds. While it is possible for the KnowledgeBuilder to build all resources found in a directory, that information is lost by the KnowledgeBuilder so those directories will not be continuously scanned. Only directories specified as part of the applyChangeSet(Resource) method are monitored.