Community
Participate
Working Groups
We need to provide the same level of support that we do for xml metadata through annotations. In addition, we will need to provide annotation support for features that are currently configurable in deployment xml and not yet supported via MOXy annotations. This work will initially be broken into the following two phases: Phase 1: provide MOXy annotation support equivalent to xml metadata support Phase 2: provide additional MOXy annotation support that allows similar configuration abilities as with deployment xml. Note that these phases will most likely be broken up into more detailed phases once further investigation is done.
After further investigation, the development phases have been updated as follows: Phase #1 – Provide MOXy annotation support equivalent to our XML metadata support Phase #2 – Provide additional support that allows similar configuration abilities as with deployment XML Phase #2.1 - Provide additional MOXy external metadata support that allows similar configuration abilities as with deployment XML Phase #2.2 - Provide additional MOXy annotation support that allows similar configuration abilities as with deployment XML
Created attachment 176706 [details] Contains proposed fix + test case modifications We now check XmlValue for type, and if not "##default" we set this type on the associated Property. Test case mods: set type in java model to Object, and set type in xml to java.lang.BigDecimal. If the type set in XML isn't processed an error will occur in the schema gen/comparison area of the test suite.
Added patch to wrong bug. Marking as obsolete.
All related bugs have been addressed. Closing as fixed.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink