Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1069288

Summary: Classes with same name break the guided rule editor if sub-fields are used
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Kralik <pkralik>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.0CC: jlocker, kverlaen, lpetrovi, rrajasek, trikkola
Target Milestone: ER2   
Target Release: 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:58:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zuzana Krejčová 2014-02-24 16:44:17 UTC
Description of problem:
Model looks like this: 

package org.pkg1;
public class Fact {
  private SubFact someField;
  ...
}

package org.pkg1;
public class SubFact {
  private Integer subfield;
  ...
}

package org.pkg2;
public class Fact {
  private String otherField;
  ...
}

In a guided rule in package org.pkg1, I set a condition with Fact from org.pkg1 and add some restriction on someField.subfield. It might look e.g. like this:
 Fact( someField.subfield > 15 )


Such a rule passes validation and can be saved, but it cannot be reopened. I get Error pop-up with quite unhelpful message "Unable to complete your request. The following exception occurred: null." Server log shows nothing.

This happens always when there are 2 classes with the same name, in different packages. The only exception is this set-up: org.Fact, org.pkg1.Fact (with SubFact attribute), org.pkg1.SubFact and the rule in org.pkg1 package.



Version-Release number of selected component (if applicable):
BPMS 6.0.1 ER1


Steps to Reproduce:
1. Create packages org, org.pkg1, org.pkg2.
2. Create POJOs (e.g. via DM)
 - Fact with String attr. in org.pkg2
 - Fact with SubFact attr. in org.pkg1
 - SubFact with Integer attr. in org.pkg1
3. Create a guided rule in org.pkg1 package.
4. Add a Condition element to the rule - Fact, add restriction on someField.subfield via the expression editor. It will look like this in the Source panel:
   Fact( someField.subfield > 15 )
5. Save the rule, (validate, check the source) close it and reopen it.


Actual results:
Error pop-up, "Unable to complete your request. The following exception occurred: null." Rule is not loaded.


Expected results:
Rule reopens.

Comment 2 Pavel Kralik 2014-03-20 13:58:15 UTC
Guided rule editor with example above works as described in "Expected results".

Verified for brms-6.0.1-ER2 deployable for eap6.