[JBoss JIRA] Created: (JBRULES-2801) Entry-point defaults for type, rule, package
by Wolfgang Laun (JIRA)
Entry-point defaults for type, rule, package
--------------------------------------------
Key: JBRULES-2801
URL: https://jira.jboss.org/browse/JBRULES-2801
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Implement the definition of the default entry point for an Event or Fact type via a metadata attribute, e.g.:
declare X
@role( event )
@entry-point( y )
end
so that this
a) declares the entry-point in the KnowledgeBase (the same way from entry-point "x" does)
b) removes the need to use from entry-point with all patterns referring to X
c) would still let me override the entry point with a "from entry-point" clause.
The same attribute can be used inside a rule, where it is associated with all fact patterns without an explicit entry point. Here it also overrides an entry-point declared with the type's declare, if any.
Since all rule attributes may also be used at package level (outside rules), this includes the new entry-point attribute. It will then be honoured in rules according to the current strategy for all other rule attributes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBRULES-2761) Restriction operator parameters should be strings, not token sequences
by Wolfgang Laun (JIRA)
Restriction operator parameters should be strings, not token sequences
----------------------------------------------------------------------
Key: JBRULES-2761
URL: https://jira.jboss.org/browse/JBRULES-2761
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Wolfgang Laun
Assignee: Mark Proctor
User defined operators (similar to "matches" or the temporal ops) may have parameters, written in '[' and ']' after the identifier denoting the relational operator. Text between the brackets is currently parsed as a "chunk", requiring the text to be composed from tokens recognized by the lexer. This is too restrictive since all Unicode characters that aren't letters (and this part of an identifier) are simply dropped.
It should be simple to parse the text between '[' and ']' as a special form of recursive string, with brackets as delimiters. This means that op[foo[1]] is OK, but op{bar[[] is not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JGRP-693) Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite
by Richard Achmatowicz (JIRA)
Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite
--------------------------------------------------------------------
Key: JGRP-693
URL: http://jira.jboss.com/jira/browse/JGRP-693
Project: JGroups
Issue Type: Task
Environment: JGroups testsuite test cases
Reporter: Richard Achmatowicz
Assigned To: Bela Ban
Fix For: 2.7
MultithreadedTestCase (MTC) is an open-source testing framework which supports the writing of multithreaded test cases. It introduces a global tick-counter which provides a deterministic form of thread synchronization, based on the number of times all threads in a test case are blocked. The tool works well ina debugger, unlike other approximate forms of synchronization (e.g. sleep())
This issue concerns using MTC in order to simplify and improve test cases in the JGroups test suite in which concurrency and blocking are at issue.
--
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
14 years, 10 months