Re: [hibernate-dev] Possibly interesting use of Jandex
But you're OK with the following instead?
@Entity
@Proxy(proxyClass=Employee.class)
class EmployeeImpl implements Employee {
...
}
?
See I find that (^^) less clear and less concise.
What's the basis for your gut to say -1? Because it "breaks" from JPA?
On Tue, Mar 11, 2014 at 5:37 AM, Hardy Ferentschik <hardy(a)hibernate.org>wrote:
On 9 Jan 2014, at 18:31, Steve Ebersole <steve(a)hibernate.org> wrote:
> Then we had expanded the previous discussion to look at the more general
> case... interface based models. Imo, the best way to map the above model
> would be:
>
> @Entity
> interface Employee {
> ...
> }
>
> Yes, this deviates from JPA which explicitly says that only classes can
be
> annotated. The question is whether we think its worthy of a "vendor
> extension".
Not sure whether I am a big fan of this. As a first gut feeling I would
give it a -1