Re: [hibernate-dev] Another @Access quandry
I have pushed the latest topical guide:
https://github.com/hibernate/hibernate-orm/blob/master/documentation/src/...
Thoughts? Comments?
The "Attribute-level" section is still undone, but I think the rest of the
text lays out the expectations in that case (especially the "Extensions"
sections) ...
On Sat, Mar 29, 2014 at 2:06 PM, Hardy Ferentschik <hardy(a)hibernate.org>wrote:
On 29 Jan 2014, at 17:59, Steve Ebersole <steve(a)hibernate.org> 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 us most flexibility. It
might create a fair bit of more work initially though.
--Hardy