The biggest issue you have to face, IMO, is getting your users to buy into a
version control\governance process.
Having them save changes as and when they see fit without some process
surrounding it will lead to a life of pain.
Any approach discussed here is a viable solution provided your users are
willing to abide by some process.
On 18 April 2011 16:20, Riyaz Saiyed <Riyaz.saiyed(a)emirates.com> wrote:
Yes, I wanted to store the entire rule set (string). But "to
re-construct"
the knowledge base from that string - for each modification request - will
have a big performance issue.
I'm open to any alternative approch with which I can meet this requirement
(while keeping the user happy :-D ).
Thanks and regards,
Riyaz..
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Decision-Table-tp2830218p2834776...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users