<i><b>Guvnor<br></b></i><br>The REST API has been most beneficial for others in your situation.<br><br>The user-guide shows how you can retrieve an asset and store it back again.<br><br><i><b>Drools Expert<br></b></i><br>There is a "fluent API" with which you can programmatically construct rules.<br>
<br>Furthermore, depending on the degree to which your rules may differ, use of Rule Templates may be an option.<br><br>I know other people are following a similar path to yourself and they should be able to talk to you about real-life experiences.<br>
<br>With kind regards,<br><br>Mike<br><br><div class="gmail_quote">On 15 November 2011 06:42, kapokfly <span dir="ltr"><<a href="mailto:ivan.jiang.ww@foxmail.com">ivan.jiang.ww@foxmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Due to some reasons (for example, build a consistent UI within our own<br>
application, easier to work with our own meta data, don't want SSO etc), we<br>
are considering to build our own UI to generate Drools rule file basing on<br>
the user input via the UI , has anyone tried this before? Is there any<br>
library shipped within Drools Gunvor can be used to be easier to work with<br>
Drools rule syntax?<br>
<br>
Thanks,<br>
Ivan<br>
<br>
-----<br>
Ivan, your Panda, forever<br>
<span class="HOEnZb"><font color="#888888">--<br>
View this message in context: <a href="http://drools.46999.n3.nabble.com/Building-our-own-UI-for-Drools-tp3508849p3508849.html" target="_blank">http://drools.46999.n3.nabble.com/Building-our-own-UI-for-Drools-tp3508849p3508849.html</a><br>
Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</font></span></blockquote></div><br>