[ https://issues.apache.org/jira/brow...action_12466319 ]

Andy Jefferson commented on JDO-403:
------------------------------------

Just remembered why I had Field.fieldType, Element.type, Key.type, Value.typ
e as String instead of Class. In the JDO2 spec we allow the implementation t
o support comma-separated sets of possible values (in particular for when th
e user has a field of type
Object with the intention of storing some specific types there, or also with
 interface fields). We have 2 options to fix this :-
1. Change the attribute back to type String and allow comma-separated like t
hat
2. Add an additional attribute "fieldTypes" ("types" in Element, Key, Value)
 of type Class[]. With this the user could either set the "type" when us
ing a single class (most common situation), or use the "types" when specifyi
ng multiple.

Interface/Property also do not currently have annotations.

> JDO2 Annotations
> ----------------
>
>                 Key: JDO-403
>                 URL: https://issues.apache.org/jira/browse/JDO-403
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2
>    Affects Versions: JDO 2 final
>            Reporter: Andy Jefferson
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: jdo_2_1_annotations.jar
>
>
> It would be desirable for JDO2 to have its own set of annotations. We have
 developed a set within JPOX that would likely serve as a starting point for
 such a set. In my opinion they should be
> 1. Split into javax.jdo.annotations.jdo and javax.jdo.annotations.orm
> 2. Move ORM attributes from some of the JDO annotations and have a ORM annotation.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://is
sues.apache.org/j...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]