Skip to main content

Home/ Java World/ Group items tagged JPA

Rss Feed Group items tagged

Hendy Irawan

Java Persistence/Caching - Wikibooks, open books for an open world - 0 views

  •  
    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.
Paul Sydney Orozco

How to Add CRUD Capability On Spring MVC using Hibernate JPA - 0 views

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

Overview of Hibernate OGM | Hibernate | JBoss Community - 0 views

  •  
    "Hibernate OGM is an attempt to store data in a NoSQL data grid using he Hibernate Core engine rather than rewriting a JPA engine from scratch. The benefits are fairly obvious: reimplementing the complex JPA specification is a lot of work a new implementation would mature at a rather slow rate and risk of bugs would be high Hibernate is familiar to many people Earlier designs for this feature in Infinispan can be found on http://community.jboss.org/wiki/DesignofJPA-likeAPIandNewFineGrainedreplication"
Hendy Irawan

Java EE 6 and Scala » Source Allies Blog - 0 views

  •  
    Last weekend while pondering the question "Is Scala ready for the enterprise?" I decided to write a simple Java EE 6 app entirely in Scala, without using any Java. I had three main reasons for doing this: one was just to see how easy/difficult it would be to write everything in Scala (it was easy).  Another was to document the process for others journeying down the same road (the entire project is on github).  Finally, I wanted to identify advantages of using Scala instead of Java that are specific to Java EE apps (I found several). Background The specific app I created was an adaptation of the Books example from Chapter 10 of Beginning Java™ EE 6 Platform with GlassFish™ 3. It's a simple web app that displays a list of books in a database and lets you add new books. Although it's a pretty trivial app, it does touch on several important Java EE 6 technologies: JPA 2.0, EJB 3.1 and JSF 2.0.
1 - 4 of 4
Showing 20 items per page