[JBoss JIRA] (RTGOV-143) Support explicitly removing event from Drools rule
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-143?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-143.
------------------------------
Resolution: Rejected
Appears that it is not possible to remove an event from an entry point (other than the default one, which is probably used for derivation rules).
So cleaning up events must be the responsibility of the CEP rule.
> Support explicitly removing event from Drools rule
> --------------------------------------------------
>
> Key: RTGOV-143
> URL: https://issues.jboss.org/browse/RTGOV-143
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
>
> Currently the rule has to indicate when an 'event' expires within the context of a rule. However if a simple derivation rule is used, this may not be specified. So an explicit flag is required to indicate that the event should be removed.
> Default behaviour should be to remove the event - so a configuration needs to explicitly indicate that the event will be cleared by the rule - to ensure that events are not inadvertently accumulated within the session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-143) Support explicitly removing event from Drools rule
by Gary Brown (JIRA)
Gary Brown created RTGOV-143:
--------------------------------
Summary: Support explicitly removing event from Drools rule
Key: RTGOV-143
URL: https://issues.jboss.org/browse/RTGOV-143
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Currently the rule has to indicate when an 'event' expires within the context of a rule. However if a simple derivation rule is used, this may not be specified. So an explicit flag is required to indicate that the event should be removed.
Default behaviour should be to remove the event - so a configuration needs to explicitly indicate that the event will be cleared by the rule - to ensure that events are not inadvertently accumulated within the session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-142) Rename CEP event processor to Drools
by Gary Brown (JIRA)
Gary Brown created RTGOV-142:
--------------------------------
Summary: Rename CEP event processor to Drools
Key: RTGOV-142
URL: https://issues.jboss.org/browse/RTGOV-142
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Implementations of the EventProcessor interface should reflect the technology used.
Other 'CEP' or 'rule' based implementations may also be provided, so shouldn't use the general concept to name the implementation class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (GADGETS-44) User Preference functionality.
by Jeff Yu (JIRA)
Jeff Yu created GADGETS-44:
------------------------------
Summary: User Preference functionality.
Key: GADGETS-44
URL: https://issues.jboss.org/browse/GADGETS-44
Project: Gadget Server and Gadgets
Issue Type: Task
Components: Gadget Server
Affects Versions: 1.0.0.M3
Reporter: Jeff Yu
Assignee: Jeff Yu
Fix For: 1.0.0.M4
Currently, the value set in the user preference won't be passed in to the gadgets.xml. specifically, can't be retrieved by using following code:
var prefs = new gadgets.Prefs();
prefs.getString(...)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients
by Kurt Stam (JIRA)
Kurt Stam created SRAMP-170:
-------------------------------
Summary: Atom feeds do not work very well in exisiting clients
Key: SRAMP-170
URL: https://issues.jboss.org/browse/SRAMP-170
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Atom Binding
Affects Versions: 0.1.1
Reporter: Kurt Stam
Assignee: Kurt Stam
Fix For: 0.2.0 - Milestone 4
Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png
When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months