ypes of composite IDs fit
>>> the same mold, which makes the source code very difficult to maintain
>>> without breaking something. IMO, composite IDs could be very much
>>> simplified if taken one use case at a time.
>>>
>>> - Original Message
s the source code very difficult to maintain without
>> breaking something. IMO, composite IDs could be very much simplified if
>> taken one use case at a time.
>>
>> - Original Message -
>> From: "Steve Ebersole"
>> To: hibernate-dev@lists.jboss.
ine the use case given the data. IMO, dealing with one use case at a
time would make the processing code straightforward and easier to maintain.
>>>>
>>>> As an example, I've listed the different types of composite IDs in
http://opensource.atlassian.com/projects/hibernate/brows
traightforward and easier to maintain.
>>>
>>> As an example, I've listed the different types of composite IDs in
>>> http://opensource.atlassian.com/projects/hibernate/browse/HHH-6234 . The
>>> old HbmBinder code attempts to have different
gt;> HbmBinder code attempts to have different types of composite IDs fit the
>> same mold, which makes the source code very difficult to maintain without
>> breaking something. IMO, composite IDs could be very much simplified if
>> taken one use case at a time.
>>
>
Original Message -----
> From: "Steve Ebersole"
> To: hibernate-dev@lists.jboss.org
> Sent: Wednesday, June 22, 2011 3:16:36 PM
> Subject: [hibernate-dev] metamodel thoughts
>
> Wanted to get my thoughts on the current state of the metamodel down so
> we could all disc
nt: Wednesday, June 22, 2011 3:16:36 PM
Subject: [hibernate-dev] metamodel thoughts
Wanted to get my thoughts on the current state of the metamodel down so
we could all discuss.
First to define some vocab for discussing. I say that the old code
(Configuration, HBMBinder/AnnotationBinder,
Wanted to get my thoughts on the current state of the metamodel down so
we could all discuss.
First to define some vocab for discussing. I say that the old code
(Configuration, HBMBinder/AnnotationBinder, mapping package) used a
"push" model. The binders interpreted the various user supplied
