surya wrote > > > By 'expensive' i mean for creating knowledgesession at runtime it depends > on various factors like: > > 1. rules reside on local file system vs on remote repository like guvnor > 2. compilation time for the rules. > 3. use case at hand and etc... > >
In our case, the rules are not complicated. Using guvnor is an option but right now I'm just thinking about doing it in the same JVM. surya wrote > > drools-camel component just makes it easy sometimes and sure it can be > done in pure drools as well. In our case we leverage on camel for several > other things and it made sense for us to rely on drools-component. > Yeah I would really like to use the drools-camel component because rest of my logic is implemented using Camel. However, if it's become really hard or I've to jump a lot of hoops to make it happen, I would go to pure drools. Another option is to modify the drools-camel component to support these features i.e., ability to add and remove rules at runtime. I'll keep you posted if I find a better way of doing this. Thanks ! -- View this message in context: http://camel.465427.n5.nabble.com/Inserting-rules-dynamically-into-camel-drools-component-tp5681880p5684012.html Sent from the Camel - Users mailing list archive at Nabble.com.
