[rules-dev] Enhancing BRDRLPersistence

Hi, This is in continuation of the mail thread in user list http://lists.jboss.org/pipermail/rules-users/2008-September/006619.html Currently we are not in a position to enhance the BRDRLPersistence to add functionality that is already supported by DRL but available in the RuleModel or in the translation. I could think of two approaches for people to write their own implementations by extending existing ones 1. Have the LHS or RHS PatternVisitor classes pluggable instead of creating the instances inside the marshalXXX methods. 2. Accept additional implementations of LHS and RHS PatternVisitor. Hence in the mashalXXX there would an additional for loop to run for each of the PatternVisitors apart from the existing for loop of each conditions or actions. If you let me know which would be preferred option I can implement the same and submit a patch. Going down the line when people write new implementations it would be easier for them to submit the patch and also make it work in their existing environment till the time the patch is not released. Even the existing classes LHS or RHS PatternVisitor need to be modified so that extending from them is easier. I will write about this in a separate mail if suggestions in this mail are acceptable. Thanks. Regards, - Nimesh MASTEK LTD. Mastek is in NASSCOM's 'India Top 20' Software Service Exporters List. In the US, we're called MAJESCOMASTEK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~