I want to run a set of rules defined in a database table with varying set of parameters.
The paramterized queries did not help as the bindings will get added over the time.
Can you suggest a best approach to design this with OCEP?
But the bindings added this way will persist after restart?
We want to maintain bindings as well in database to update in future.
To explain the scenario better:
A processor is supposed to read rules and the binding parameters from DB and run them against the stream.
Edited by: user8906186 on Apr 5, 2012 6:05 AM
You could try doing this directly through the service interfaces com.bea.wlevs.ede.api.Processor and com.bea.wlevs.ede.api.Statement.
Another option is to still use the MBeans, but always delete and re-load respectively when shutting down and re-starting the server to keep things in sync with an external source.