[JBoss JIRA] Created: (JBRULES-2730) Duplicate rules name errors not being identified across multiple resources in same package
by Michael Pellegrini (JIRA)
Duplicate rules name errors not being identified across multiple resources in same package
------------------------------------------------------------------------------------------
Key: JBRULES-2730
URL: https://jira.jboss.org/browse/JBRULES-2730
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Windows XP, Java 1.6.0_17
Reporter: Michael Pellegrini
Assignee: Mark Proctor
The validateUniqueRuleNamesmethod in the org.drools.compiler.PackageBuilder class currently only checks for duplicate rule names that are defined within the same resource. However, in the case where there are multiple resources added to the knowledge builder that share the same package name then the validateUniqueRuleNames method is not detecting duplicates across the package.
In cases where rules have the same name and are defined in the same package then I would have expected to get a duplicate rule error but I do not as the rules are physically reside in two separate resources.
It seems logical that in addition to checking if any rules are duplicated within the resource that it also checks to see that rule was already defined in the package registry as well. Otherwise the last rule overwrites the first and creates some rather odd behavior.
--
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-1007) Flush: change signature of JChannel#startFlush to include checked exception
by Vladimir Blagojevic (JIRA)
Flush: change signature of JChannel#startFlush to include checked exception
---------------------------------------------------------------------------
Key: JGRP-1007
URL: https://jira.jboss.org/jira/browse/JGRP-1007
Project: JGroups
Issue Type: Task
Affects Versions: 2.6, 2.8
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 3.0
We have to change signature of startFlush method to include checked exceptions in its signature. We have previously relied on boolean return value of startFlush to get information about success of startFlush method invocation. This approach has been proven to be insufficient, particularly in the light of dealing with [JGRP-985]. We need to discriminate various reasons why startFlush failed, i.e due flush collision, missing response from flush member and so on. Therefore, starting with release 3.0 startFlush method will be void and will throw checked exceptions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months