JPA persistance best practices and orm configuration….Tomcat configuration tips
June 24th, 2008
The issues of persistance have taken the most of my sparetime recently as I have planned the implementation details of JPA entity layer…
good basis for investigation have provided the 2 series of peristance provided by IBM Developerworrks articles..namely
Patterns of persistence, Part 1: Strategies and best practices for modern ORM tools
and Patterns of persistence, Part 2: Increase code reuse and enhance performance,other useful links are oracle’s best basic Java
Persistance API practices article and the JEE blueprints of persistance….
as recommeded in the basic Java Percstance API practices the Integration with Spring is fabulous combination ….in addition if you utilize hibernate enity interceptors as was the case in IBM persistance series the configuratio with spring is done in the folllowng way http://forum.springframework.org/archive/index.php/t-10512.html and voila you get the benefit of the auditing features of JPA enity modifications and updates…
Enabling compression on the web server will make data be transferred in compressed form. The browser will decompress the data on the fly, making the application faster. If your application uses Ajax, what usually increases the volume of data transferred from server to client, compression of data will significantly improve your application performance.
Here is how to enable GZIP compression on Tomcat: edit file /conf/server.xml and add to the HTTP Connector configuration something like this:
Entry Filed under: Java, J2EE, Tomcat, Java JPA, JEE Blueprints, JEE
WordPress database error: [Can't open file: 'wp_comments.MYI' (errno: 144)]
SELECT * FROM wp_comments WHERE comment_post_ID = '55' AND comment_approved = '1' ORDER BY comment_date
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed