Internal Website Search

the web-app from Tomcat's manager? Should I set some kind of listener ? Yotam Yotam Boaz You can set a listener for creating and destroying the EntityManagerFactory: https://www.objectdb.com/tutorial/jpa/eclipse/web/ listener When the application is stopped by the Tomcat manager the 

there is: void postDirty(InstanceLifecycleEvent event) http://www.objectdb.com/api/java/jdo/ listener ... can see, there are: a) Lifecycle Listener classes, e.g: http://www.objectdb.com/java/jpa/persistence/event and b ... -commit' listener .  I can guarentee single threaded access to a single EntityManager in an embedded

Hi, wondering if it's possible to listen for changes in one process from another process? ie: process A changes an entity process B listens for @PostPersist   thanks   dmoshal David Moshal This is not supported. You may be able to implement your own cross process event listeners based

entityManagerFactory = (...); entityManagerFactory.setEntityFactory(myFactory); The JPA listeners ... listener instances inside his application and add this listener via API call to ObjectDB (like ... the EntityManager in a JPA listener method by using JDO:     EntityManager em

subsystem 13:49:26,858 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /127.0.0.1:9999 ... initialized event to listener instance of class guest.GuestListener: javax.persistence ... _ObjectDB_web]] (MSC service thread 1-3) Exception sending context destroyed event to listener instance

INFO  [org.jboss.as.remoting] (MSC service thread 1-13) JBAS017100: Listening on localhost/127 ... : Listening on /127.0.0.1:9999 13:52:02,439 INFO  [org.jboss.as.server.deployment.scanner] (MSC ... :03,175 INFO  [org.jboss.as] (MSC service thread 1-11) JBAS015951: Admin console listening

.remoting] (MSC service thread 1-10) JBAS017100: Listening on /127.0.0.1:9999 08:17:22,672 INFO [org.jboss.as.remoting] (MSC service thread 1-11) JBAS017100: Listening on localhost/127.0.0.1:4447 08:17 ... listening on http://127.0.0.1:9990 08:17:23,457 INFO [org.jboss.as] (MSC service thread 1-12

.. } and listener like below: public class MyListener {     @PostLoad     ... Weishaupt This is an unexpected exception. It is thrown during analysis of the listener class in

sending context initialized event to listener instance of class OcspServer.CertEntryListener java.lang ... The database location is specified on: http://www.objectdb.com/tutorial/jpa/eclipse/web/ listener

.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999 04:56:02,526 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on localhost/127.0.0.1:4447 04:56

the listener during run, and not by the Maven enhancement that failed. Your solution solves the problem ... . With the domain class project, I also have "Entity Listeners " so I omit those packages, but I'm a bit

released some of these objects, reducing the number from 1860 to 1149. The ObjectDB server listens ... to stop ServerSocket listening :      https://stackoverflow.com/questions/2983835

specifies a TPC port on which the server is listening for new connections. Usually the default port 6136

Is there a listener or program that can be used to sync across data from/to MySQL and ObjectDB so that I can use ObjectDB for development and then just make sure MySQL always has the same data? ThreaT Ashton Hogan There are plans to implement such a tool. You may subscribe to this feature request

cannot be cast to database.entity.Player, Listener : { Ext: TestServer, Type: JAVA, Lev: ZONE, { Zone

; Perhaps setting ObjectDB to use weak references but then using persistent object callback/ listeners to track

to listen to client requests. When the connection is closed on the client side (including on client

Hi, I'm wondering how best to be able to detect if ObjectDb Server is alive? For: a) from a java process - I'm guessing you could try and grab a Persistence Manager and/or listen for a Disconnection Exception?? b) from a NodeJs runtime - I'm guessing you could either try and grab the ObjectDb

Hi Please help me.I have requirement like In my project having arround 100 pojos .I have used @EntityListener and @prePersist annotaions to invoke my action class .. But problem is how can i get oldvalue and new value of current form of pojo in side my @entity Listener Action class. code snipt

you can still use JPA annotations to set cascading operations. Alternatively you may be able to listen

; moreover that exception is raised before any preStore callback or listener so I could not check field structure and I'm

to which the embedded server is listening by adding a port argument to the url that is used to open the database in

.persistence.ArgumentException: The filter listener "matches" requires a constant argument.  

some "doBeforeDie" method before the deletion. You may define a callback or listener for JPA

listener or callback . support Support Build 2.4.7_01 adds simple text logging of query execution

has to set listeners for these events and then notify other applications and servers. support Support

the master and the slave. The slave keeps listening for updates from the master and applies any update

property or listener fires and causes an error while ObjectDB is loading the data - clearly my fault not

listeners for pre persisted and post persisted in order to check the entity version number. For example

. using a contextDestroyed listener ? During the last corruption did you have hot deployments (i.e

Fixed 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.

.internal. listeners .RequiementHierarchyConstraintsEnforcerListener.handleEvent

Improved recovery from failure when recovery is enabled with no sync  ( issue #2293 ). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading ( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed

. Towfique Imam Thank you for this report. There was a problem in handling listeners and callback methods