db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig Russell <Craig.Russ...@Sun.COM>
Subject Re: Support java.lang.Object as FCO
Date Wed, 17 Aug 2005 20:18:05 GMT
Hi Andy,

On Aug 17, 2005, at 10:39 AM, Andy Jefferson wrote:

> Hi Michelle,
>> It seems that jpox maps Object as serialized by default.  Where  
>> there is
>> no serialized or embedded attribute on the field, we map to a FK  
>> column,
>> e.g. OBJECT102 BIGINT REFERENCES SIMPLE_CLASS, giving a jpox error:
> Well we interpret all types as serialized="false", but in section  
> 18.14 of the
> spec "java.lang" types (which Object is) are to be embedded="true" by
> default. So we interpret this as serialising the Object into the  
> table of the
> class, into a BLOB column.

I tried to be more explicit about this in the Proposed Final Draft,  
to say that embedded="true" doesn't mean serialized but embedded  
column by column. Just like embedded PC instances.

Could you please take a look at the PFD and see if this is not clear  


>> SimpleInterface, which we map identically to Object, works fine.
> Because we treat an Interface as embedded="false" by default (since  
> it's not
> specified in the list of embedded types in 18.14, so its effectively a
> PersistenceCapable in that respect).
> -- 
> Andy

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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message