> On Oct 28, 2016, at 10:34 AM, Andy Jefferson <a...@datanucleus.org> wrote: > >> 1. New JIRA JDO-757 "Add @Repeatable to all annotations which can be >> repeated" https://issues.apache.org/jira/browse/JDO-757 >> >> Looks like we are almost done here. No need to deprecate existing >> “repeatable container” annotations. If any user really wants to use them, >> fine. > > Well there would be zero point in deprecating them since they are required > for @Repeatable to work, hence they can never be deleted.
I did not realize this. Good to know. > >> Question: >> why was ElementType.TYPE added to Column? What does this mean? > > Means that when @Column annotation was originally added it was incorrect. > @Column on a class is to define "unmapped columns" to equate to <column> just > under <class> in XML. Apparently the unmapped column paradigm has exactly one use case: /** * Value to be inserted when this is an “unmapped” column * @return the value to be inserted when this is an “unmapped” column */ String insertValue() default ““; It looks like there is no tck test for this. Oh Well. > When adding @Repeatable the compiler tells you about such errors so had to be > fixed (so that the singular annotation with @Repeatable is consistent with > the container annotation). Looks good. I think we’re done here. Craig > > > > Regards > -- > Andy > DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus) Craig L Russell Architect craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
