[JBoss JIRA] Created: (JBRULES-432) DSL aware editor
by Michael Neale (JIRA)
DSL aware editor
----------------
Key: JBRULES-432
URL: http://jira.jboss.com/jira/browse/JBRULES-432
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
In this editor, drop downs will be provided to choose expressions from the lists of templates (it won't be a text editor), with the "data" being populated with a text box.
The work for parsing can be done server side, the editor only has to display+capture data values from the user.
A basic implementation would be something like:
* A DSL aware editor would be good. This works as the following (assuming Google GWT):
- Is implemented as a subclass of Widget or Composite in GWT (refer to the GWT manual)
-Takes in a DSL via public methods: setDSLConditionList(String[] list) and setDSLActionList(String[] list) for completion lists.
-Takes in rule in the form of:
-setLHS(String[]) -lists of conditions
-setRHS(String[]) - list of actions
-After a rule has been edited, the resulting text can be obtained by String getLHS(), getRHS etc.
-User can chose an icon to popup a list of conditions to add, actions to add (chosing from respective list)
-User can chose to remove a condition, or an action (by clicking on a "-" next to a condition or action)
COMPLEX BITS:
-User can choose to edit a line of the rule (if they are allowed to). In this case, it may get a bit complicated. It may go back to the server and get a list of labels/fields which it can then display to the user so they only edit the fields. An alternative, is to do some processing on the server before the rule is loaded, and provide all the lines not as a string, but as a list of labels/fields.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBRULES-428) Access Control List - each node to be protected
by Michael Neale (JIRA)
Access Control List - each node to be protected
------------------------------------------------
Key: JBRULES-428
URL: http://jira.jboss.com/jira/browse/JBRULES-428
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
Rule nodes (at least) need to have an ACL: what groups can access it in what capacity. First need to have a structure for ACLs to be stored.
They should be tied to user groups/roles, not individual logins.
JAAS should provide the user name and the users context (group membership) I believe.
When there is an ACL, it must be checked to see if the user (via their group membership) can do one of the following:
Edit, change status, view, delete.
If they can't view, ideally it will not be shown in any "lists", but if that is not feasable, it would be acceptable to list it, but not show the contents.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months