FactType object instantiated outside drools no longer match rules in 6.3.0.Final -------------------------------------------------------------------------------- Key: DROOLS-1070 URL: https://issues.jboss.org/browse/DROOLS-1070 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.3.0.Final Environment: Java 8 (1.8.0_72) Reporter: Jogchem de Groot Assignee: Mario Fusco There's a problem of regression between the drools 6.2.0.Final and 6.3.0.Final releases: In 6.2.0.Final the following was possible: - You could create a FactType (for example a Data Object in the workbench) in your knowledge base - From your application code, after loading the knowledge base. You could obtain the specific FactType from the knowledge base, get the class and instantiate a new instance of that class, effectively being a new instance of the FactType. - This new instance of the FactType could then be inserted into a drools session for the knowledge base and would be succesfully matched by rules that match the FactType as defined in the knowledge base. In 6.3.0.Final these rules would no longer be activated as the new FactType instance would be loaded by a different class loader (and thus is a different class) than the FactType class that the rules are trying to match. Therefore: in 6.3.0.Final it's no longer possible to define your business objects in your rule base, but have them populated and supplied outside of the rule session (in your application code).