8 | Auto Date for Creation and Update methods are invoked. You may want to check @PostPersist and other callbacks as |
8 | Automatic schema evolution causes ArrayOutOfBoundsException callback method. The second schema change is supported and should be handled automatically by |
8 | Method Invocation On All Entities the deletion. You may define a callback or listener for JPA lifecycle events (see this manual page |
8 | Show Sql/Jpql queries). You may log these operations by setting a JPA lifecycle listener or callback. support |
8 | Partial Indexing. You can keep that partial field synchronized with the main field by using a callback method (which will be annotated |
8 | Failed to read the value of field using reflection to ConcurrentHashMap (and added a converter callback attached to @PostLoad event so I get my concurrent |
1 | Blocked by find - Error sending callback event rbccm.felix.framework.ApplicationException: Error flushing data |
1 | ObjectDB 2.1.1Fixed an Explorer bug in handling listeners and callbacks. Fixed a bug in using user/password url arguments multiple times. Fixed several bugs in query processing and running. |
1 | @PrePersist not working correctly the event callback method. Notice, however, that using merge as a replacement of persist is inefficient |
1 | InternalException - error reading field from "queue" databaseI trying to use an objectdb database as a persitent queue but have started getting the following error on the receiver side: 2011-07-25 10:54:25,023 AdminServer-Callback-Instance-2/0 ERROR ServiceRunner - Error processing message. rbccm.felix.framework.ApplicationException: Error taking message |
