|
This is part of an e-mail that I sent to a number
of people recently. I would like to hear any and all comments from the rules
community on this subject. <James, you have already had your
turn>.
"It looks like AspectJ is very complementary to rules programming.
The
caveat would be that it now introduces an even higher level of abstraction - and since most people find it hard to deal with the inherent abstraction of rules programming to begin with then this would certainly send them over the edge (or over to Burger King for a new job). On the other hand hand, if this is the wave of the future then it brings a new insight into rules programming: actually using requirements to identify the "concerns" of inferencing as part of analysis, design , and implementation. That is an awesome dark hole out there. Nobody seemed to be able to deal with this on any of the rules projects I have seen - the "web weenies" don't use requirements, analysis, or design in a rules engineering environment." Thanks,
Rich Halsey
|
- JESS: AspectJ and Rules Rich Halsey
- JESS: AspectJ and Rules Rich Halsey
- RE: JESS: AspectJ and Rules James Owen
