Bug 731668
Summary: | Changing model's package doesn't import it's types. | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Zuzana Krejčová <zkrejcov> |
Component: | BRM (Guvnor) | Assignee: | manstis |
Status: | VERIFIED --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | BRMS 5.2.0-ER1 | CC: | manstis |
Target Milestone: | --- | ||
Target Release: | BRMS 5.3.0.GA | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously when changing the package a model belongs to in the JBoss BRMS user interface, the model's types were not automatically imported and the user had to perform this step manually. This issue has been resolved and it is no longer necessary for users to perform the step manually.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
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á
2011-08-18 09:35:19 UTC
Agreed, it is not a good state. Its a feature that we should tackle in 5.3 Please clarify what you mean by "when you change a model's package"? Do you mean the Java classes in the POJO model are moved to a different package and a new POJO JAR uploaded? (In reply to comment #2) > Please clarify what you mean by "when you change a model's package"? Do you > mean the Java classes in the POJO model are moved to a different package and a > new POJO JAR uploaded? That should have meant a package in Guvnor, like the (present by default) defaultPackage and Global Area or mortgages for the sample repository. And moving the model from let's say mortgages to defaultPackage. As in open the asset, model, in Guvnor switch to its attribute view and click on the pencil next to the "Package: <somePackageName>" row, then choose a different package. I hope it's clearer now. Fixed in master and back-ported to 5.3.x. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously when changing the package a model belongs to in the JBoss BRMS user interface, the model's types were not automatically imported and the user had to perform this step manually. This issue has been resolved and it is no longer necessary for users to perform the step manually. |