openjpa

I'm using OpenJPA and I have a lock problem. I already understand what's an OptimisticLockException and when it's thrown. But how can I deal with it ? Below*, you can find a small paragraph about the optimistic lock exceptions. In a nutshell, how I can totally disable the lock manager ? In my persistent.xml, I have the following xml code but it does not work. Why ? ... <properties> <property name="openjpa.LockManager" value="none" /> </properties> ... *According to the wikibooks about the Java Persistent : Handling optimistic lock exceptions Unfortunately programmers can frequently be too

Is anyone successfully using OpenJPA with Glassfish? I'm trying to use OpenJPA 2.1 with Glassfish 3.1 Open Source. I've followed the instructions to integrate the two here -> http://weblogs.java.net/blog/ss141213/archive/2006/07/using_openjpa_a.html I have a very simple EJB project in Eclipse Indigo with the following: com.rares.test.Person - @Entity com.rares.test.PersonManager - interface com.rares.test.PersonDao - @Stateless However, when I try to deploy I get a ClassNotFoundException on my Person @Entity. The complaint seems to be the Person parm on a create method that's being implemented

I'm new to JPA/OpenJPA and I noticed that if I don't call EntityManager.clear() after i persist entities I get an OutOfMemoryError (I keep adding new entities in a loop). I'm not sure if this is the expected behavior or it's just and OpenJPA 1.2.1 glitch. So, am I required to explicitly detach the entities myself? If I'm not, it's a good practice anyway? I don't have much experience with JPA. However this'll be useful - In JPA you must either: - Create a new EntityManager for each transaction. - Call clear() after each transaction to clear the persistence context. Depends how many objects you

By looking into the Open JPA website i've found that i can log the generated SQL by using the following: <property name="openjpa.Log" value="DefaultLevel=WARN, Runtime=INFO, Tool=INFO"/> If i try to add the above property to my persistence.xml i get the following warning from weblogic: <Warning> <J2EE> <BEA-160202> <You have specified a ope njpa.Log setting in your configuration for persistence unit services.ear#services-ejb.jar#exp#exp. This setting will be ignored, and all log messages will be sent to the WebLogic logging subsystem. Trace-level logging is controlle d by the various JPA

In my web applicaton I use OpenJPA on Apache Tomcat (TomEE)/7.0.37 server. I use Netbeans to auto generate class ("Entity Class from database..." and "Session Beans From Entity Class..."). At SessionBean (for example UserFacade) i want to get EntityManager: @Stateless public class UserFacade extends AbstractFacade<User> { @PersistenceContext(unitName = "CollDocPU") private EntityManager em; @Override protected EntityManager getEntityManager() { return em; } } but when i get it by above way I get null. When I make it by: @Override protected EntityManager getEntityManager() {

In one to many JPA associations is it considered a best practice to initialize relationships to empty collections? For example. @Entity public class Order { @Id private Integer id; // should the line items be initialized with an empty array list or not? @OneToMany(mappedBy="order") List<LineItem> lineItems = new ArrayList<>(); } In the above example is it better to define lineItems with a default value of an empty ArrayList or not? What are the pros and cons? JPA itself doesn't care whether the collection is initialized or not. When retrieving an Order from the database with JPA, JPA will