[JBoss JIRA] Created: (JBRULES-3205) Add 'name' and 'description' attributes to <Resource> element in change-sets
by Esteban Aliverti (JIRA)
Add 'name' and 'description' attributes to <Resource> element in change-sets
----------------------------------------------------------------------------
Key: JBRULES-3205
URL: https://issues.jboss.org/browse/JBRULES-3205
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Esteban Aliverti
Assignee: Esteban Aliverti
Priority: Optional
Fix For: 5.4.0.Beta1
It would be good the possibility to add (a optional) 'name' and 'description' to each Resource in change-set. These attribute should be exposed by org.drools.io.Resource
Even if these attributes don't have any effect in Resource's behavior and functionality, they will server as documentation of the change-set.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (JBRULES-3197) simple declaration flagged in RHS code, dialect "mvel"
by Wolfgang Laun (JIRA)
simple declaration flagged in RHS code, dialect "mvel"
------------------------------------------------------
Key: JBRULES-3197
URL: https://issues.jboss.org/browse/JBRULES-3197
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.3.0.Beta1
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.3.0.CR1
The declaration of variable i is flagged as an error, with
a funny error message: variable defined within scope: i,
as if there ever were a variable that is *not* defined
within its scope!
Expected behaviour is to accept this declaration.
rule KickOff
dialect "mvel"
when
then
int i;
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Resolved: (JBRULES-3063) Drools should not allow set two rules with the same name for the same package
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3063?page=com.atlassian.jira.plug... ]
Edson Tirelli resolved JBRULES-3063.
------------------------------------
Assignee: Edson Tirelli (was: Tihomir Surdilovic)
Fix Version/s: 5.3.0.Final
(was: FUTURE)
Resolution: Done
This was implemented by:
1. Adding support to the Knowledge Builder to report results of different severities: INFO, WARN, ERROR
2. Raising a result message for rule and function replacements.
3. Adding a configuration to allow users to define with which severity some messages should be reported. E.g., a rule replacement (duplication) could be reported as an INFO, WARN or ERROR.
Errors prevent package compilation, while warnings and info don't.
> Drools should not allow set two rules with the same name for the same package
> -----------------------------------------------------------------------------
>
> Key: JBRULES-3063
> URL: https://issues.jboss.org/browse/JBRULES-3063
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: drools-compiler
> Affects Versions: 5.1.1.FINAL
> Reporter: Alessandro Lazarotti
> Assignee: Edson Tirelli
> Priority: Minor
> Fix For: 5.3.0.Final
>
>
> Drools should not allow set two rules with the same name for the same package
> As expected, Drools does not allow us to define two rules with the same name in a same DRL file.
> But if there are two rules with the same name, in the same package, but in separate files, no exception or warning is issued, just one rule overrides the other in silence.
> From documentation:
> "A rule must have a name, unique within its rule package. If a rule is defined twice in a single DRL, an error will appear when one loads it. If a DRL that includes a rule name already in the package is added, the previous rule is repalced."[1]
> [1] http://docs.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/JB...
> Different behavior for a similar action is not good. Both should alert user about a rule name repeated.
> For large projects using a lot of DRL files can be hard to track mistakes occurred by rules override . It is really necessary provide an ERROR message for this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months