Craig's summary is what I was trying to get at. Char and byte arrays are persistable by default. Other types require the PersistentCollection annotation, and can be handled as collections or lists.
Some changes to the metamodel generator and to the runtime appear to be required. I think we're generally in agreement though. -mike On Thu, Jun 30, 2011 at 10:29 AM, Pinaki Poddar <[email protected]> wrote: > Mike, > Primitive arrays especially for byte and char being treated as a singular > attribute is something intuitively appealing. If I get the drift of your > suggested modification, the array of entities would continued to be treated > as par collection. Is that right? > > OpenJPA mostly treats ARRAY and COLLECTION in the same breath. At a first > glance, it may take some effort to make special provisions based on an > array's component type. Or may be there is a short cut at the facade level > model to make such provision up front. My memory of Metamodel > implementation > is fading... > > ----- > Pinaki > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Metamodel-generates-ListAttribute-for-arrays-instead-of-SingularAttribute-tp6529049p6533762.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. >
