07-23-07 12:11 PM
[ https://issues.apache.org/jira/brow...action_12514571 ]
Craig Russell commented on JDO-510:
-----------------------------------
I agree. We can add a Persistent[ ] members() default {} to @Persis
tenceCapable to do this easily enough. We can use the @Persistent(name="supe
rclassName" ...) with whatever overrides are needed.
But note that the spec doesn't allow for changing the persistenceModifier of
a superclass field or property. From 18.15, " The persistence-modifier attr
ibute can be specified only for fields declared in the Java class, and not f
ields inherited from superc
lasses. " But mapping certainly can be overridden.
> Remove @Field and @Property and replace them with @Persistent
> -------------------------------------------------------------
>
> Key: JDO-510
> URL: https://issues.apache.org/jira/browse/JDO-510
> Project: JDO
> Issue Type: New Feature
> Components: api2
> Reporter: Craig Russell
> Assignee: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
> Attachments: jdo-510.patch
>
>
> Annotations are different from xml ways that make it impossible to refer to persis
tent fields and properties in the same way. We started out thinking that we could si
mply map the xml field to annotations @Field and xml property to @Property but could
no
t refer to multiples in a sane way.
> This change removes @Field and @Property and replaces them with @Persistent. Other
annotations that refer to these are changed so that they refer to members instead o
f to fields or properties.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ Post a follow-up to this message ]
|