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

Bug 1067885

Summary: In projects where data modeler fails to open data model, Form modeler does not see any DM classes
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jan Hrcek <jhrcek>
Component: Form ModelerAssignee: Walter Medvedeo <wmedvede>
Status: CLOSED NOTABUG QA Contact: Jan Hrcek <jhrcek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: pzapataf, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-21 13:43:18 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:
Attachments:
Description Flags
Screenshot showing the problem none

Description Jan Hrcek 2014-02-21 09:41:59 UTC 
Created attachment 865888 [details]
Screenshot showing the problem

Description of problem:
This is most likely a result of Bug 1066600 but I'm opening this to make engineering aware of another issue that might be caused by externally modified data modeller classes.


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

How reproducible:
Always

Steps to Reproduce:
1. Create a new form in project, that contains externally modified data modeler classes (as mentioned in Bug 1066600)
2. In Form Modeler go to Form Data Origin and select Type: from data model

Actual results
No class is available in 'Info' select, that normally contains all data modeler classes from the current project

Expected results:
Data modeler classes should be available in Form Modeler.
Comment 1 Pedro Zapata 2014-02-21 11:28:53 UTC 
If classes don't pass the compilation stage due to any error in the code or build problem, they won't be loaded and visible through the ProjectDataModelOracle interface. That means they can't be listed or referenced from any other part of the platform (including form modeler).

There's nothing that can be done for this in all situations. If the problem relies on the platform introspection mechanism, it can be fixed. If the problem relies on the code committed, and classes don't compile, they can't be listed (=search in classpath).
Comment 2 Rajesh Rajasekaran 2014-02-21 13:43:18 UTC 
Based on the comment above, closing this issue as NOTABUG.