Mark Proctor <mproctor <at> codehaus.org> writes: > > The descr is a string based intermediate API. Its a rough appoximation > to the classes rule/spi except each field is just a string. The > PackageDescr is then passed to the PackageBuilder which returns a > Package. We have aligned Drools 3.0 with Java - RuleSets no longer > exist, we just call them Packages. It is possible to go direct to > rule/spi - especially if you have no code to compile - but bear in mind > that PackageBuilder has a lot of logic to take care of the building and > you might end up replicating a lot of it anyway. > > Take a look at PackageBuilder and RuleBuilder in drools-compiler. > > I would love to have a RuleML driver - but its complex and is marked for > after 3.0. So a directly aligned XML was a quick answer to those that > still need XML. Also remember that RuleML has some limitations - for > instance you can't have freecode in predicates and consequences - > instead you can only call functions. > > Mark
So our first objective is to derieve an XSD for native rule representation, if I have gotten it right. Then we can move on to a conversion logic using a mapping tool. Please let me know of any documents or tutorials to understand the DRL used now
