Technically, this is feasible, but consider the following issues:
- You will have to save the entire ruleset as a string
- If you only save part of the ruleset as string: how are you going to
decide which part and how are you going to combine this with the other
rules?
- You will have an incredible abundance of duplicate rule strings, most of
them exaclty the same as a lot of other rule strings.
Riyaz Saiyed wrote:
The initial idea was to save a rule string as additional column in
database with every booking request (against each product). Next time for
any modification (for same product), I can create a .drl file from
previously stored string at runtime and execute the rule again.
-With best regards,
Riyaz
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Decision-Table-tp2830218p2834397...
Sent from the Drools: User forum mailing list archive at
Nabble.com.