...
| Tip | ||
|---|---|---|
| ||
It is not strictly necessary to qualify imported types or fields providing the name is unambiguous across all of a model's imports. However, it is best practice to use the qualified name as it insulates the model from future changes to imports that may cause an unqualified reference to become ambiguous in the future. |
| Note | ||||||
|---|---|---|---|---|---|---|
| ||||||
Types from a model imported must be generated with the same encoding type as the model importing them. It is not possible to mix and match different encoding types within a message or entity. So if MessageA is generated with Xbuf and embedded EntityB is generated with Protobuf, Message cannot use EntityB as a field.
When generating code and copying model to output, encoding information is written to target model XML as a directive. If model for which code is generated and any of its imports have encoding mismatch, code generator will raise model validation error. For imported models that do not have encoding info (resolved directly to OS path or packaged to jar with earlier versions of ADM), this validation is not enforced. |
...