Description of problem:
When you upload a POJO model, it's types are automatically imported into it's package. When you change the model's package, those types aren't imported into the new package, you have to do it manually, one by one. Can be very annoying for larger numbers of imported types.
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.
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.