 6 | -capable classes and to perform common operations needed by implementations, not by end users ... . There is no security restriction on this access. JDO implementations get access to the functions provided by this class only if they are authorized by the security manager. To avoid having |
6 | : Constants This class can be used by a JDO-aware application to call the JDO behavior ... managed by the PersistenceManager. This method returns a copy of the ObjectId that represents ... . If the JDO identity is managed by the application, then the ObjectId may be used |
6 | ) are thrown by the Java Virtual Machine or can be thrown by the Java throw statement. Similarly ... , and so on, leading to a "chain" of exceptions, each caused by another. One reason that a throwable may have a cause ... thrown by the lower layer propagate outward, as it is generally unrelated to the abstraction provided |
5 | of entity classes and to keep them simple as possible. Retrieval by Class and Primary Key Every entity object can be uniquely identified and retrieved by the combination of its class and its primary key ... except that if the entity object is not already managed by the EntityManager a hollow object |
5 | result by specifying this annotation in the metadata. Example:
Query q = em.createNativeQuery(
"SELECT o.id AS order_id, " +
"o.quantity AS order_quantity, " +
"o.item AS order_item, " +
"i.name AS item_name, " +
"FROM Order o, Item i |
5 | the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright ... and all other entities that control, are controlled by, or are under common control with that entity |
5 | is not initialized, and may subsequently be initialized by a call to initCause. Since: Java JDK1.0 ... be initialized by a call to initCause. Parameters: message - the detail message. The detail message is saved for later retrieval by the getMessage() method. Since: Java JDK1.0 Exception(Throwable cause |
5 | Well ! I think i pointed out a HUGE performance issue with mapped-by attribute (yeah ... , go the MyEntity class and remove "mapped-by". You obtain 1 second max of query fetch. So my performance issue ... .ALL,mappedBy = "myEntity") // Test by adding / remove "mappedBy"
public MyEntityChild getEntityChild |
5 | , Object obj)" method which is synchronized and attempts to load an object by id using the EntityManager ... .ObjectDbInstanceContainer@9c71a4 owned by: DEV1-WSAgent-1-Existing/3
Total blocked: 190 Total waited: 69 ... : BLOCKED on com.objectdb.o.LKM@254e85f4 owned by: ODB-FileWriter
Total blocked: 789 Total waited: 616 |
5 | and using. We find a slow memleak in our application recently, and by trace of Entity construct and finalize, we found the problem is caused by bad state of EntityManager. After first throwing ... and retrieved by EntityManagerFactory, and the instances of Entity constructed by ObjectDB |