Group items tagged

Sample of using Hibernate Annotations by reducing XML configuration files thus making it simpler to define required metadata directly into our Java code. When using annotations, we no longer need the additional mapping file (*.hbm.xml). The metadata for the ORM is specified in the individual classes.

" Everthing Object Teams - adding team spirit to your objects. Object Teams with Null Annotations without comments The recent release of Juno M4 brought an interesting combination: The Object Teams Development Tooling now natively supports annotation-based null analysis for Object Teams (OT/J). How about that? :)"

An Example explaining on how @Required annotation from Spring Framework works. Provides sample on how to use @Required and expected exception if beans are not properly configured like BeanInitializationException or Property is required for bean.

Spring 3.0.5 is now released and comes with the fixes of more than 80 minor issues and provided some enhancements and improvements to the Spring Expression Language (SpEL), annotation support, and embedded databases.

JAX-RS 1.1 offers a @ApplicationPath annotation applicable to javax.ws.rs.core.Application which let you specify the webcontext and remove the need for any web.xml

"Morphia is a lightweight type-safe library for mapping Java objects to/from MongoDB: Easy to use, and very lightweight; reflection is used once per type and cached for good performance. Datastore and DAO access abstractions, or roll your own... Type-safe, and Fluent Query support with (runtime) validation Annotations based mapping behavior; there are no XML files. Extensions: Validation (jsr303), and SLF4J Logging"

Caching is the most important performance optimization technique. There are many things that can be cached in persistence, objects, data, database connections, database statements, query results, meta-data, relationships, to name a few. Caching in object persistence normally refers to the caching of objects or their data. Caching also influences object identity, that is that if you read an object, then read the same object again you should get the identical object back (same reference). JPA 1.0 does not define a shared object cache, JPA providers can support a shared object cache or not, however most do. Caching in JPA is required with-in a transaction or within an extended persistence context to preserve object identity, but JPA does not require that caching be supported across transactions or persistence contexts. JPA 2.0 defines the concept of a shared cache. The @Cacheable annotation or cacheable XML attribute can be used to enable or disable caching on a class.

A step by step tutorial on adding CRUD (Create,Read,Update,Delete) capability on Spring MVC using Hibernate JPA.

The TypeScript compiler infers the type information when there is no explicit information available in the form of type annotations.