Search This Blog

JPA Performance settings Explained

Lets consider this simple Entity, Ignore @SecondaryTables and other annotations if you are not familiar with just focus on @Basic, @OneToOne, @OneToMany annotations and get ready to answer these questions.

Are just "hints" to the JPA provider and its not mandatory for JPA provider to implement them, So their is no quarantee that these objects when loaded will be lazily loaded.

Conclusion : Entities heavily using above annotations and also if we load and them in bulk could seriously cause performance bottlenecks, however there are nice ways of loading entities with trim data using "Contructor" Queries. which will be topic of my next thread.

"FetchType fetch (Optional) Whether the value of the field or property
should be lazily loaded or must be eagerly fetched. The
EAGER strategy is a requirement on the persistence provider
runtime that the value must be eagerly fetched. The
LAZY strategy is a hint to the persistence provider runtime.
EAGER "

@OneToOne(fetch=FetchType.LAZY)JPA 2.0 Specification document Page 402Also have the same comment

@OneToMany(fetch=FetchType.LAZY)JPA 2.0 Specification document Page 400Also have the same comment

What is CsvValidator ?
A Java framework which validates any CSV files something similar to XML validation using XSD.

Why should I use this ?
You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference.

Why did I write this ?
Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing.