<div dir="ltr"><span style="font-size:12.8000001907349px">Hi</span><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">After a very long development cycle, we have finally introduced CDI and JPA technologies into oVirt.</div><div style="font-size:12.8000001907349px">This means that in the next few month you'll see more and more of our stored procedures replaced with JPA code, which will allow us to have easier entity mapping and enjoy performance boost with caching.</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">Some things to keep in mind:</div><div style="font-size:12.8000001907349px">1. When implementing a DAO class, please make sure to annotate it with the @Named and @Singleton annotations.</div><div style="font-size:12.8000001907349px">2. The engine-daos.properties file is no longer needed, and is removed from our code.</div><div style="font-size:12.8000001907349px">3. If you want to migrate your own DAO to work with JPA, please look at the Bookmark, BookmarkDaoDbFacadeImpl and BookmarkDaoTest classes (see patch <a href="https://gerrit.ovirt.org/#/c/33836/">https://gerrit.ovirt.org/#/c/33836/</a>).<br><br></div><div style="font-size:12.8000001907349px">There is a simple infrastructure that will allow you to do most of the things you need quite easily. If something is missing - please drop me an email to <a href="mailto:lzelkha@redhat.com" target="_blank">lzelkha@redhat.com</a> - I'll be happy to assist.</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">Thanks for everyone who took part in this effort - Oved, Moti, Roy, Yevgeny and everyone else. </div></div>