Hi Rahul,

Its not about storing the whole file into the database.

I would have a Table representing the parameteres required to construct a rule.

For example.

Tables:

RuleSetTable:
Ruleset_id
Ruleset_name

RuleTable:
Rule_id
Rule_name
Rule_saliance
Rule_condition
Rule_consequence
Ruleset_id

Now while loading the rules the application basically should read from the DB, and construct the rules, as everything required to construct the rules is avaliable in the tables.

This requirement had come up because as the rules keep changing quite frequently, we don't want to bring down the application to load a new DRL file.

Hope you understood what I want to achieve.

Thanks much,
Sandeep.