<font size=2 face="sans-serif">For #1 and #2, I am planning on using DSL
that uses a separate model, built specifically for rule writing, that wraps
around the actual application domain model. DSL sentences are not quite
as user friendly, the rule writer has to pick from a huge list of DSL sentences
as opposed to incremental condition phrase building available from the
native rule editor, but there is no other way, short of building your own
rule editor.</font>
<br>
<br><font size=2 face="sans-serif">The common rulesets, due to their very
nature, I am not exposing to the clients for editing, they are internal.
The KnowledgeBuilder api can load common rules (which could be in .drl
files) in addition to guvnor rules.</font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Ghanshyam</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">kapokfly <ivan.jiang.ww@foxmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">rules-users@lists.jboss.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">11/16/2011 08:16 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [rules-users]
Building our own UI for Drools</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">rules-users-bounces@lists.jboss.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi GPatel,<br>
<br>
Maybe separate by package is something can be tried, but do you see the<br>
functionality of what Gunvor provided is good enough for your usage? <br>
<br>
For us it is still missing some necessary functions:<br>
given a condition, 'a = b', <br>
1) we would like the 'b' part could be an expression/reference to another<br>
field, not only a value<br>
2) we would like to be able to redefine the dot notation so it can refer
to<br>
not only a property but also its meta data information so the meta data<br>
value can also be used as part of the rule <br>
3) for existing none object graph traverse we also would like to register<br>
our own property resolver so it can load related objects into the proper<br>
context <br>
<br>
Also are you able to tweak the UI to comply with your own application's<br>
style?<br>
And does your object also share a common rulesets across different<br>
customers? How you design this part in your POC so any potential upgrade<br>
could be easier? <br>
<br>
Ivan<br>
<br>
-----<br>
Ivan, your Panda, forever<br>
--<br>
View this message in context: </font></tt><a href="http://drools.46999.n3.nabble.com/Building-our-own-UI-for-Drools-tp3508849p3512962.html"><tt><font size=2>http://drools.46999.n3.nabble.com/Building-our-own-UI-for-Drools-tp3508849p3512962.html</font></tt></a><tt><font size=2><br>
Sent from the Drools: User forum mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
rules-users@lists.jboss.org<br>
</font></tt><a href="https://lists.jboss.org/mailman/listinfo/rules-users"><tt><font size=2>https://lists.jboss.org/mailman/listinfo/rules-users</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
-----------------------------------------
The information contained in this communication (including any
attachments hereto) is confidential and is intended solely for the
personal and confidential use of the individual or entity to whom
it is addressed. If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that you have received this
communication in error and that any review, dissemination, copying,
or unauthorized use of this information, or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original
message. Thank you