The main additions needed for round trip of the basic Type and Property
information (not yet addressing other XSD information) are:
For multi-valued properties that are not using generics (ie
List<Customer>), and when the instance class is not enough to resolve
the Type of the Property (primarily for new DataTypes), the Property
Type should be indicated.
For bidirectional properties, the opposite Property needs to be
For containment properties, containment true/false needs to be
For types, open and sequenced needs to be indicated.
We think that the scope of this is too big for 2.1 and that it should be
considered for 3.0 instead. In addition, the solution should work for
both statically generated and dynamic DataObject and it's unclear how an
annotation approach would solve both of these cases.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.