ss it like it does any other
>> composite. This is because everything routes through the same "build
>> attribute binding" code no matter where the attribute comes from. I had
>> already fixed this in the annotation source code using a "attribute builder
>> str
fix a problem.
>
>
>
>
> On Mon, Apr 14, 2014 at 3:55 PM, Gail Badner wrote:
>
>> Also inline...
>>
>> - Original Message -
>> > From: "Steve Ebersole"
>> > To: "Hardy Ferentschik"
>> > Cc: &
uot;Hardy Ferentschik"
> > Cc: "Hibernate"
> > Sent: Saturday, April 12, 2014 11:55:28 AM
> > Subject: Re: [hibernate-dev] Some thoughts on possible Binder changes
> >
> > Thanks for the response. See inline...
> >
> >
> > O
Also inline...
- Original Message -
> From: "Steve Ebersole"
> To: "Hardy Ferentschik"
> Cc: "Hibernate"
> Sent: Saturday, April 12, 2014 11:55:28 AM
> Subject: Re: [hibernate-dev] Some thoughts on possible Binder changes
>
> Thanks f
Thanks for the response. See inline...
On Sat, Apr 12, 2014 at 1:15 PM, Hardy Ferentschik wrote:
>
> On 12 Jan 2014, at 18:56, Steve Ebersole wrote:
>
> > The Background
>
> ...
>
> Thanks Steve, for this really nice summary. It is always good to share
> some basic design/implementation
> deta
On 12 Jan 2014, at 18:56, Steve Ebersole wrote:
> The Background
…
Thanks Steve, for this really nice summary. It is always good to share some
basic design/implementation
details.
> In terms of dealing with composite ids, step (1) really just means creating
> the Embeddable "shells" (the Emb
The Background
Binder deals with dependencies between things. An Entity cannot be fully
bound until its attributes and identifier are fully bound. An Embeddable
cannot be fully bound until its sub-attributes are fully bound. One Entity
might depend on another by nature of a "key many to one" or
