[hibernate-dev] Another @Access quandry

Steve Ebersole steve at hibernate.org
Wed Mar 26 15:27:08 EDT 2014

Well we are in the position we are in already from one person making this
determination ;)

So that is the situation I am trying to avoid.  As this thread is showing,
we all have different readings/interpretations of the same spec passages.
 It is good to come to a consensus.

On Wed, Mar 26, 2014 at 2:21 PM, Hardy Ferentschik <hardy at hibernate.org>wrote:

> On 26 Jan 2014, at 20:16, Steve Ebersole <steve at hibernate.org> wrote:
> > Ok, but... its still a good spring board to discuss this topic which is
> strangely unclear and murky in terms of what we do and do not support.
> Sure. I am just saying, we are discussing a wrong test. When I was
> implementing the JPA @Access rules, I never had the intentions to support
> the mapping which started the this thread. In my interoperation of the JPA
> spec it is wrong. It should either thrown an exception (in fact I thought
> there
> used to be some checks which would actually do that) or if anything just
> ignored the annotation.
> --Hardy

More information about the hibernate-dev mailing list