I don't want to use an ORM like Hibernate. Maybe I have to use something from Oracle. I don't know. If I use EJB3 and the EntityManager, will that implement the JPA standard, so I can write regular SQL queries. I like using raw SQL, but I don't want to embed SQL in my program. If my ideas are wrong on what the EntityManager is, I'm trying to figure out that too.
Main thing is no embedded SQL so that I don't have to recompile each time I change something. If I use JDBC that's fine, but again I don't want to have to recompile each time.
No ORM (at least not Hibernate, TopLink, etc.) I understand what an ORM is, the mismatch between objects and relational data. I just don't want to use one.
Can I have the best of both worlds?
Will I have to make my own DAL?
Jeanne Boyarsky wrote:EJB 3 uses JPA for EntityManager. Standalone Java also uses JPA for EntityManager. EntityManager is an interface. JPA/EntityManager *are* an ORM. So by definition, the answer to your question is "no."
You could use JDBC and put the SQL queries in a property file.
If I do that last one and say read my queries from an xml file, is that something that's not usually done? Is it a bad way of doing things?
Does that mean I will have to build my own DAL to make relational data objects?
author & internet detective