The Artima Developer Community
Sponsored Link

Java Buzz Forum
JPA and CMT – Why Catching Persistence Exception is Not Enough?

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
justin cater

Posts: 9927
Nickname: justin78
Registered: Mar, 2011

Justin Cater is executive editor at Java Code Geeks
JPA and CMT – Why Catching Persistence Exception is Not Enough? Posted: Mar 27, 2013 1:57 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by justin cater.
Original Post: JPA and CMT – Why Catching Persistence Exception is Not Enough?
Feed Title: Java Code Geeks
Feed URL: http://feeds.feedburner.com/JavaCodeGeeks
Feed Description: Java 2 Java Developers Resource Center
Latest Java Buzz Posts
Latest Java Buzz Posts by justin cater
Latest Posts From Java Code Geeks

Advertisement
Being in EJB and JPA world using CMT (Container Managed Transactions) is very comfortable. Just define few annotations to demarcate transaction boundary (or use the defaults) and that’s it – no...

Read: JPA and CMT – Why Catching Persistence Exception is Not Enough?

Topic: Git Submodules: Core Concept, Workflows And Tips Previous Topic   Next Topic Topic: Defining EJB 3.1 Views (Local, Remote, No-Interface)


Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2014 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use - Advertise with Us