I have a couple of questions from an application development perspective. 1. Does anyone know what the 'best practice' for organisation of drl files is. All the examples just seem to show an application using a single drl file. Is there logically a concept that you have a drl file that is just logic for a particular context of the application in one drl file and separate logic in another drl file. If so how do you load up those rules into your rule base? Is it a case that you load up the rule base using the RuleBaseLoader and a particular drl file at a point in the application to where it applies? BTW I'm not referring to use of Entities here because that still boils down to one big drl file in the end that has to be parsed.
2. I am presuming that RuleBase instance/s should be loaded up at application initialisation and then a new WorkingMemory created when the rules are to be fired. Not sure if this is the case or not as the code examples are not clear on this. I'm just looking at it from a performance optimisation perspective. Regards Paul Smith
