Depending on your model, it may be better to create a DSL as an intermediate language. That way you have a simplified language, which you control, to parse in and out, which could be tuned to your own domain model.SteveOn 19 Mar 2013, at 14:36, kurrent93 <[hidden email]> wrote:HI DavidYes we are also looking into rule templates.We have come up with - what we believe - is a very natural, intuitive and visually appealing way to author rules. And it is tailored for our specific domain.One significant aspect of our work is that we are present drools authoring to end users - customers - rather than business users. Hence the importance of crafting a specialized UI, rather than the generic UI of Guvnor.And FYI - are also including in the design some UI elements, for a future version, that will use Drools Chance features.Can you point me to documentation - and ideally - samples around using APIs for the descriptor level?ThanksOn Tue, Mar 19, 2013 at 3:11 PM, Davide Sottara [via Drools] <<a href="x-msg://398/user/SendEmail.jtp?type=node&node=4022881&i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote:
As a RETE network is being created, DRL Rules are parsed into an internal "descriptor" structure (a high level AST)
and then compiled into a RETE.
There are "APIs" to create rules at the descriptor level: this can then be "dumped" back into DRL.
To work at the DRL level directly, it's common to use parametric "templates".
If your internal (meta)model is object oriented, you could consider using DRL rules to write the translators :)
Davide
p.s. could you provide some more information about your use case? I'm doing some research on rule authoring
environments right now. Thanks!
On 03/19/2013 09:54 AM, Michael Anstis wrote:
Rules are DRL that is a String.
Where and how you choose to store the String is up to you.
Please try to explain what you want to achieve a little more.
On 19 March 2013 12:49, kurrent93 <[hidden email]> wrote:
HI all
Is there any samples or documentation for reading and writing of rules?
The user case is we are trying to build a custom Rule Editor, and thus would
like to write and read rules to/from our beans.
Thanks
--
View this message in context: http://drools.46999.n3.nabble.com/API-for-reading-and-writing-rules-tp4022874.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________ rules-users mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
http://drools.46999.n3.nabble.com/API-for-reading-and-writing-rules-tp4022874p4022878.htmlIf you reply to this email, your message will be added to the discussion below:To unsubscribe from API for reading and writing rules, <a href="x-msg://398/" target="_blank" rel="nofollow" link="external">click here.
NAML
View this message in context: Re: [rules-users] API for reading and writing rules
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users
http://drools.46999.n3.nabble.com/API-for-reading-and-writing-rules-tp4022874p4022885.htmlIf you reply to this email, your message will be added to the discussion below: