Sorry for talking to myself :)
> Thinking more about trimming, I am becoming more and more convinced that
> CHAR should be treated as fixed size char[] in Java as well, just like
> byte[] (via wrapper type 'CharacterArray' to track changes - like Andrus'
> NSData-like ByteArray wrapper idea).
Alternatively we could just avoid custom wrapper types (to lessen an
application model dependency on cayenne) and just require explicit
touching of the owning DataObject via setXX(byte[]/char[]). No copying,
just requiring the same char[] to be set again so that the DataObject can
change its persistence state. Seems a reasonable compromise to me,
especially since Strings have to be set as well; it would be more in line
with value object usage pattern (although the byte/char[] itself is
mutable).
Holger
This archive was generated by hypermail 2.0.0 : Tue Mar 04 2003 - 06:20:50 EST