Hi. Seems that a common use-case will be initial creation of POJOs via the Data modeler and subsequent refinement of those POJOs by more specialized tools. ie; via JBDS: add JPA/Hibernate or JAXB annotations. Afterwards, further changes to those now JPA or JAXB annotated POJOs in the Data Modeler should not over-write nor eliminate those annotations. At least in BPMS6.0.0.GA, the data modeler removes the annotations that have been tacked on to POJOs external of the data modeler. thanks! jeff
This might be considered as a duplicate of bug 1061350.
Annotations preservation will be delivered for community version 6.1, and after that included in next GA version.
Annotations preservation was implemented and pushed in master branch, so the feature should be testable in community 6.1.CR releases.
The feature was implemented in both 6.2.x community and 6.1.0 CR1 releases.
It seems that annotations disappear above constructors. Classes, methods and fields works fine. Moving back to Assigned.
One remark about this. For drools purposes it's necessary automatically generate four constructors. Empty constructor (no arguments), a constructor with all fields, a constructor with all fields annotated as @Position, and a constructor with all fields annotated as @Key. Because of that constructors are re-generated, when new fields are added, or annotated, etc. For this version it was defined that constructors will be created and deleted again. This explains why constructors can loose annotations. But this is part or current definition.
Walter, I believe the correct behavior is to not override existing constructors. The 4 constructors you mentioned are created as helpers, there are no hard requirements that depend on such constructors (other than the no-arg constructor), so the best thing to do is to preserve existing constructors and just add new constructors if they do not exist.
The criteria for generating the constructors were changed, and now existing user generated constructors are preserved. Data modeller generated constructors are still generated but only when they don't conflict with user generated ones. This new criteria solves the issue. master URL: http://github.com/droolsjbpm/kie-wb-common/commit/e822d9333 master URL: http://github.com/droolsjbpm/kie-wb-common/commit/d9812a09e push 6.2.x URL: http://github.com/droolsjbpm/kie-wb-common/commit/3a73a8c55 push 6.2.x URL: http://github.com/droolsjbpm/kie-wb-common/commit/f3fa0582b PS: This commits includes some modifications that solves the following BZs. https://bugzilla.redhat.com/show_bug.cgi?id=1173075 https://bugzilla.redhat.com/show_bug.cgi?id=1173089
Annotations above the constructors don't disappear anymore. Verified with ER5.