The JPA 2 metamodel is the cornerstone of type-safe criteria queries in JPA 2. The generated classes allow you to refer to entity properties using static field references, instead of strings. (A metamodel class is the fully-qualified class name of the entity class it matches followed by an underscore (_)).
IntelliJ now has support for the new JPA 2.0 typesafe query facility I've beenbloggingabout. It's very important that this stuff works smoothly with tooling, so it's great to see that the tooling vendors are on this early.
Haha, just stumbled across this. It's funny to see, a whole three years after the end of the Persistence Wars, and in the face of the incredible success of JPA in almost every corner of Java development, that the conspiracy theorists are still out there, darkly hinting that commercial organisations like Oracle, IBM, RedHat ... have their own vested interest in RDBMS technologies, or in selling application servers.
What, you didn't think it was possible? Of course it is! Although the Seam development team encourages you to use Hibernate as the JPA provider, Seam is capable of working with any JPA provider. This entry will show you how.
There's been plenty of discussion in the JPA group about my
typesafe criteria proposal.
My new favorite feature of the Java language
Java 6 annotation processors are derived from the APT tool that
existed in JDK 5, but are built into javac. Really, the name
annotation processor is misleading, since this feature is only
incidentally related to annotations. The Processor is really a
fairly general purpose compiler plugin. If, like me, you've never been
a fan of code generation, now is the time to reconsider. A Java 6
The public draft of the JPA 2.0 specification is already out and includes a much-awaited feature: an API that lets you create queries by calling methods of Java objects, instead of by embedding JPA-QL into strings that are parsed by the JPA implementation. You can learn more about the API proposed by the public draft at Linda's blog.