I could suggest lots of features :-)
But, from Ent to Ent, let's not be too hasty. I have suggested adding support for getting the DRL file name and line number (of the line where keyword 'rule' is), collected by the actual DRL compiler, available from the Knowledge Builder. Also, other attributes are available from the compiled rule, although only from the "unstable" version of class Rule; the real metadata is available even in the "stable" version.
So I see a way of getting the salient information and DRL code chunks without a (possibly gullible - what about /*-comment?) DRL parser. (Meanwhile, I'm veryfying the results of my own very crude parser by checking against the KnowledgePackages.)
I'll keep watching the development and contribute my ideas (and some code) on Rule Documentation.
-W
On 17 September 2010 16:01, Toni Rikkola <toni.rikkola@gmail.com> wrote:
The drools-docs module is one of those things that I have been working on when I have some extra time. So right now there is no work going into it.
Yes the Metadata should be renamed. Its too easy to confuse with the rule metadata.
Any help is welcomed, like always :-) Even if it just suggested features.
ToniOn Fri, Sep 17, 2010 at 2:54 PM, Wolfgang Laun <wolfgang.laun@gmail.com> wrote:
_______________________________________________I've just discovered this, although apparently experimental, it's quite nice.
Will this approach be continued and extended?
Note that "Meta Data" should be written as "Metadata".
And the "metadata" grabbed from comments isn't the "real" rule metadata.
-W
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev