Mark,
kindly READ what I write: In JIRA-3386 NONE of the words
"rule", "agenda-group", "ruleflow-group" etc. appear: it
requests bulk retrieval for OTHER top level items declared
in DRL that can already be retrieved individually by full name.
[But since you mention these attributes and their impending
doom: Removing agenda-group and its brethren is going to be a
tough nut, with all the DRL code up and about that uses
these features, their being entrenched in spreadsheets
and the Guvnor knows where else. So you think that adding
a few calls in the API is going to make their extinction
more difficult? Really? Really!? (These are rhetorical questions
so there's no need for an answer.)]
Regards
Wolfgang
On 14 February 2012 20:52, Mark Proctor <mproctor(a)codehaus.org> wrote:
On 14/02/2012 04:51, Davide Sottara wrote:
> Wolfgang, could you please open a JIRA for this?
This is related to my reluctance to expose agenda-groups, salience
grousp and other rule meta data on the Rule interface.
Part of my reason for that is we only just got a clean api and we know
that agenda-group, ruleflow-group etc will be changed. So I'm trying to
be forward thinking on not bloating the external api. Also where does it
end? Do we expose the entire LHS/RHS, etc?
A compromise is we could create a secondary helper class that will get
those attributes values.
RuleMetaHelper.getSalience( rule );
RuleMetaHelper.getAgendaGroup( rule );
RuleMetaHelper.getRuleflowGroup( rule );
Mark
>
> --
> View this message in context:
http://drools.46999.n3.nabble.com/Once-more-why-why-why-is-this-user-prov...
> Sent from the Drools: Developer (committer) mailing list mailing list archive at
Nabble.com.
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev