db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: Embedded object and evict
Date Thu, 28 May 2009 18:11:18 GMT
I agree that embedded objects should be included in the spec. Right  
now, there are hints but no specified behavior for embedded objects  
with regard to the life cycle interrogatives and the behavior at  
commit and evict.

I think the best approach is to treat embedded objects as transient  
for all of the life cycle interrogatives. Then there is no question  
about expected behavior after evict, commit, etc.

This does impact design. If you choose to make an embedded object,  
then that object only has persistent behavior when associated with an  
owner. It's never dirty, and can't be the parameter of any of the life  
cycle changing APIs.


On May 26, 2009, at 3:14 AM, Christiaan wrote:

> Does this need to be addressed in the spec? Personally I feel that  
> this
> technical design issue really impacts the decision of a designer  
> whether a
> class should be embedded or not, whereas I think it should be a  
> conceptual
> decision whether a class should be embedded or not. So making it more
> explicit in the spec would at least be one thing to do.
> -- 
> View this message in context: http://www.nabble.com/Embedded-object-and-evict-tp22738918p23720315.html
> Sent from the JDO - Development mailing list archive at Nabble.com.

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

View raw message