Hide Forgot
Description of problem: Building packages via Guvnor with built-in selectors doesn't work as expected. Each build contains all the rules in the package, not just those intended for the build. Steps to Reproduce: For example,starting with empty repository, install samples when asked. 1. In "mortgages" package, "Edit" view, select "Use built-in selector" and the option "When category: = Pricing rules" 2. Build the package. (3. You can check the assets included via output in terminal or KnowledgeAgent->KnowledgeBase->KnowledgePackage.) Actual results: All the rules (and other assets) get included in the package. Expected results: Package with only the "Pricing loans" rule. Additional info: Curiously enough, custom selectors work well, both java class files and drl files.
Unless this can be shown to be a regression, this is a candidate only for this release.
Zuzka, is this a regression compared to BRMS 5.1?
No regression, worked the same way in 5.1. Sorry for the delay.
Fixed. Please note, selectors have no effect on package source code, check https://issues.jboss.org/browse/GUVNOR-108.
Hi Jervis, I trying to figure out what is needed for the release notes for this issue. Guvnor-108 explains the way selectors should work, has anything changed here? I only ask because the issue is listed as being ON_QA, but from Guvnor-108 I wouldn't have expected anything to change. Thanks Lee
Hi Lee, as far as the release note is concerned, it should be enough to say that this issue fixed the problem described by this issue, i.e: "Building packages via Guvnor with built-in selectors doesn't work as expected. Each build contains all the rules in the package, not just those intended for the build."
Thanks Jervis, I've marked this issue as not needing a release note, as the issue reported was in fact the correct behavior.
Hi Lee, the problem reported by this issue is indeed a bug. The issue has been fixed in this release.
Hi Jervis, this doesn't look ideal yet. Though most cases work. I have categories like this: cat1 cat2 cat2/cat3 and rules: rule1 in cat1 and cat3 rule2 in no category If I choose to build a package with rules NOT in cat3: rule1 gets included, though it should not be, and rule2 isn't included though it should be.
This issue is not raised as a blocker for this release. Therefore it is rejected for the current release and will be proposed for the next release.
So generally built-in selector works now, though there r still 2 edge cases that it failed to handle properly: 1. When the asset has not category 2. When the asset has more than one categories and the operator is "!=".