Christian Beikov
Christian Beikov
Would you mind rebasing this please @david-kubecka ?
Thanks for the report. I haven't seen this sort of behavior yet, but I'll look into it as soon as possible.
I guess we could do something special here for the id like e.g. call `PersistenceUnitUtil.getIdentifier` which would allow accessing the identifier on a proxy without initializing. The workaround is to...
The annotations on the entity. You should put all annotations on the getters instead of the fields.
If you change to property access, embeddables will also use property access, unless you annotate them with `@Access(FIELD)`. If you have an association or basic value that defines a column...
The problem here really is the fact that we need some kind of context to do "the right thing" for e.g. collection defaults etc. Builders need the static metamodel to...
The static metamodel is initialized during the bootstrap of the EVM, similar to the JPA static metamodel being initialized during the bootstrap of the EMF. The EVM is the context.
Sounds good to me
Sorry, but implementing this is quite hard as the query language, is pretty complicated. We already have a JPA Criteria implementation though. Maybe that's good enough for you for now?
>Debugging shows that BP is confused by the overridden name attribute in the entities. When converting the EV instance into the entity it assigns `BoyView.name` to `Child.name` while `Boy.name` stays...