Just to bring this back up one more time :)
I plan on going this route in Hibernate 5. Specifically the part where
using @Proxy with proxyClass as an interface registers the entity under
that interface name rather than the under the class name. This gives
us the ability to expose parameterize
Oops, forgot the name of the test package I referred to :)
org.hibernate.test.dynamicentity
On Wed 21 Mar 2012 08:06:44 AM CDT, Steve Ebersole wrote:
> Comments inline...
>
>
> On Wed 21 Mar 2012 05:36:01 AM CDT, Sanne Grinovero wrote:
>> As an API user if I'm expected to use the _User_ interface
Comments inline...
On Wed 21 Mar 2012 05:36:01 AM CDT, Sanne Grinovero wrote:
> As an API user if I'm expected to use the _User_ interface, I think I
> would expect the annotations to be defined on the interface, not on
> the UserImpl.class .. as with the rest of mapping annotations.
>
> I don't
As an API user if I'm expected to use the _User_ interface, I think I
would expect the annotations to be defined on the interface, not on
the UserImpl.class .. as with the rest of mapping annotations.
I don't know about the technical requirements to make this
implementable; I guess you need some U
Forwarding a part of this discussion that got inadvertently limited to
just Sanne and myself.
Bringing this back up because this is most likely not going to be
accepted into JPA 2.1. Anyway, I am all for going down the path that:
public interface User {
...
}
@Entity
@Proxy(proxyClass=User.cl
