[rules-dev] Why are fundamental API functions not part of "stable"?
Wolfgang Laun
wolfgang.laun at gmail.com
Sat Aug 21 02:54:18 EDT 2010
On 20 August 2010 21:56, Mark Proctor <mproctor at codehaus.org> wrote:
>
> try this:
> for ( KnowledgePackage pkg : kbase.getKnowledgePackages() ) {
> for ( org.drools.definition.rule.Rule rule : pkg.getRules() ) {
> String name = rule.getName();
> org.drools.rule.Rule realRule = ( org.drools.rule.Rule
> ) ((KnowledgePackageImp)pkg).getRule( name );
> System.out.println( realRule.getAgendaGroup() );
> }
> }
Very well hidden - almost an 'Easter egg ;-)
Thank you!
> At the drl it'll stay, for backwards comptability for a while, we'll map
> it onto the new planned constructs. I have plans over all for something
> more generic, orthogonal and thus more flexible and powerful.
At one time, I thought that the metadata map would be the place where
things are kept. - I canimagine that a selection mechanism based on
s.th. like general property predicates would give you all you've got now
(possibly even with long-term backward compatibility) and plenty of new
possibilities. "Sharing" of rule sets among focusable grouds is one thing
I'd very much like to have...
-W
More information about the rules-dev
mailing list