Eric Miles wrote:
I'm going through some code and I came across something that
make much sense to me. Can someone explain to me the design behind
tieing a ruleflow to a package? I'm trying to programmatically build
some rulebases together and just realized I can not add a ruleflow to a
rulebase directly unless it has already been added to a package (thus
when I add the package to the rulebase, the ruleflow is indirectly
added). This doesn't seem completely right and would like some
clarification on why.
The Package is our general unit of deployment produced by the
PackageBuilder, it can build rules and processes. A Ruleflow needs
building and compiling and the end result needs to be stored somewhere,
it made sense just to store it in our existing Package object.
rules-users mailing list