To wrap this up..
The most important part for me is being able to identify the point between
the "attribute base" and the "attribute path". If we just use a separate
delimiter there, that's enough for me. Since one of us has a preference
for using dots within the "attribute path" part (and its i
Since there seems to be no unanimous consensus, the majority consensus
seems to be to for that (1) approach. So that's going to be my working
principle here for now.
Another thought...
Again to me this all comes down to 1 concept in JPA being used to represent
3 different things. That's never a
On 29 Jan 2014, at 17:59, Steve Ebersole wrote:
> Again to me this all comes down to 1 concept in JPA being used to represent 3
> different things. That's never a good situation. So maybe internally we
> start representing all 3 distinctly.
That’s sounds like a good idea which would give
On 28 Jan 2014, at 13:55, Steve Ebersole wrote:
>
> On Mar 28, 2014 7:27 AM, "Hardy Ferentschik" wrote:
> >
> >
> > On 28 Jan 2014, at 12:47, Steve Ebersole wrote:
> >
> > > Given the problems using byteman is causing in CI
> >
> > What problem is that?
>
> Port contention of some sort
Is t
On 29 March 2014 16:40, Steve Ebersole wrote:
> To wrap this up..
>
> The most important part for me is being able to identify the point between
> the "attribute base" and the "attribute path". If we just use a separate
> delimiter there, that's enough for me. Since one of us has a preference
>
