Internal Website Search

1-50 of 134 results

JPA Lifecycle Events

for that operation. Listeners and External Callback Methods External callback methods are defined outside entity classes in a special listener class: public class MyListener { @PrePersist void ... (in a listener class) should always return void and take one argument that specifies the entity

Step 3: Add a Context Listener Class

closing the EntityManagerFactory . To register a ServletContextListener : Open the [New Listener ... Other... Web Listener and clicking Next . The Java package name should be guest. Enter GuestListener ... All to enable the Finish button. Click Finish to create the new listener class. Now replace the content

Step 3: Add a Context Listener Class

Other... Select Web Web Application Listener and click Next . Enter GuestListener as the class name ... to create the new listener class. Now replace the content of the new source file with the following

How to define Default Entity Listeners without persistence.xml and orm.xml

Listeners . How to do ? Here my init code: Properties config = new Properties(); config.put("javax ... Mahmoud Defining default listeners is one of the few things that currently require XML metadata. You cannot define default listeners using annotations (at least in JPA 2.0). support Support

listening on a particular IP aside localhost

to listen in server mode to other connections from another machine where client is installed. I ... 8888 in configuration file but I wasn't able to add listening ip address such as 192.168.50.56 olyjosh Joshua Aroke ObjectDB will listen automatically to all requests to the server on which it is running

Entity listener - event instead of object

Hi, Currently I'm playing with entity listener to implement auditing with difference between ... to obtain an EntityManager from a listener class? You may use the JDO getPersistenceManager method ... and I'm already subscribed. The main problem for me was to get EM inside listener class. Hibernate uses

Safe to monitor listening port by connect/disconnect?

I wish to monitor our instances of ObjectDB using an automated tool that simply connects and then disconnects from the ObjectDB listening port once per second (frequency is configurable).  Will this cause any issue with the normal operation of ObjectDB? CAPdev CAP Dev It should be fine.  support Support

JDO External Listeners

The following types can be used to implement external listener classes for JDO lifecycle events: Listener objects can be bound to one or more persistence capable classes by invoking the addInstanceLifecycleListner method either at the PersistenceManagerFactory level or the PersistenceManager level.

ObjectDB Object Database Features

callback methods and listener classes . JDO callback methods and listener classes. Primary Keys

JPA Annotations for Callback Methods

The following annotations can mark methods as JPA callback methods: The Lifecycle Events section of the ObjectDB Manual explains how to use all these annotations on callback methods and with listener classes.

Server Configuration

on which the server is listening for new connections. Usually the default port 6136 should be specified

Database Replication and Clustering

these details to connect to the master server in order to listen to updates. The updates

Database Connection using JPA

(could be a domain name or an IP address) and listening on the specified port (the default is 6136

JPA Annotations for Classes

JPA defines three types of persistable classes which are set by the following annotations: Chapter 2 of the ObjectDB manual explains these annotations in detail. Entity and mapped super classes can be further configured by annotations that specify cache preferences and lifecycle event listener

Database Server

The TPC/IP port on which the server listens for new connections is also specified in the Server

Step 2: Define a JPA Entity Class

a context listener class that will manage a JPA's EntityManagerFactory representing the ObjectDB database.

Step 2: Define a JPA Entity Class

listener class that will manage a JPA's EntityManagerFactory representing the ObjectDB database.

[ODB1] Chapter 8 - ObjectDB Server

configuration TCP port to listen to To start the server, use the start command: java com.objectdb ... when you extract a newer version of the ObjectDB server. The TPC port on which the server is listening ... are required. The port attribute specifies the TPC port on which the server will be listening

PersistenceManagerFactory.addInstanceLifecycleListener(listener,classes) - JDO Method

; InstanceLifecycleListener   listener ,    Class[] classes ) Add the parameter listener to the list of instance lifecycle event listeners set as the initial listeners for each ... to the listener . The listener will be called for each event for which it implements the corresponding

PersistenceManagerFactory.removeInstanceLifecycleListener(listener) - JDO Method

;  InstanceLifecycleListener   listener ) Remove the parameter listener instance from the list of instance lifecycle event listeners set as the initial listeners for each PersistenceManager ... : listener - the listener instance to be removed Since: JDO 2.0

PersistenceManager.addInstanceLifecycleListener(listener,classes) - JDO Method

; InstanceLifecycleListener   listener ,    Class... classes ) Adds the listener instance to the list of lifecycle event listeners . The classes parameter identifies all of the classes ... for which it implements the corresponding listenerInstance interface. Parameters: listener

PersistenceManager.removeInstanceLifecycleListener(listener) - JDO Method

JDO Method in javax.jdo.PersistenceManager void removeInstanceLifecycleListener (    InstanceLifecycleListener   listener ) Removes the listener instance from the list of lifecycle event listeners . Parameters: listener - the listener instance to be removed Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleListener

JDO Interface InstanceLifecycleListener All lifecycle listeners extend from this base interface. In order to minimize the impact on domain classes, instance callbacks can be defined to use a life-cycle listener pattern instead of having the domain class implement the callback interface(s). Since: JDO 2.0

javax.jdo.listener.StoreLifecycleListener

JDO Interface StoreLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of store events. Since: JDO 2.0 Public Methods void postStore ( InstanceLifecycleEvent  event) Invoked whenever a persistent instance is stored

javax.jdo.listener.LoadLifecycleListener

JDO Interface LoadLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of load events. Since: JDO 2.0 Public Methods void postLoad ( InstanceLifecycleEvent  event) Invoked whenever a persistent instance is loaded from the data

javax.jdo.listener.InstanceLifecycleEvent.ATTACH

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent ATTACH Since: JDO 2.0

javax.jdo.listener.DeleteLifecycleListener

JDO Interface DeleteLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of delete events. Since: JDO 2.0 Public Methods void postDelete ( InstanceLifecycleEvent  event) Invoked whenever a persistent instance is deleted

javax.jdo.listener.CreateLifecycleListener

JDO Interface CreateLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of create events. Since: JDO 2.0 Public Methods void postCreate ( InstanceLifecycleEvent  event) Invoked whenever an instance is made persistent

javax.jdo.listener.ClearLifecycleListener

JDO Interface ClearLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of clear events. Since: JDO 2.0 Public Methods void postClear ( InstanceLifecycleEvent  event) This method is called after the ClearCallback.jdoPreClear

javax.jdo.listener.AttachLifecycleListener

JDO Interface AttachLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of attach events. Since: JDO 2.0 Public Methods void postAttach ( InstanceLifecycleEvent  event) This method is called after a detached instance

javax.jdo.listener.InstanceLifecycleEvent.DELETE

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent DELETE Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent.CLEAR

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent CLEAR Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent.DETACH

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent DETACH Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent.DIRTY

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent DIRTY Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent.CREATE

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent CREATE Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent

JDO Class InstanceLifecycleEvent java.lang.Object ∟  java.util.EventObject ∟  javax.jdo. listener .InstanceLifecycleEvent This is the event class used in life cycle event notifications. Note that although InstanceLifecycleEvent inherits Serializable interface from EventObject, it is not

javax.jdo.listener.InstanceLifecycleEvent.STORE

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent STORE Since: JDO 2.0

javax.jdo.listener.InstanceLifecycleEvent.LOAD

JDO Static Field in javax.jdo. listener .InstanceLifecycleEvent LOAD Since: JDO 2.0

javax.jdo.listener.DirtyLifecycleListener

JDO Interface DirtyLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of dirty events. Since: JDO 2.0 Public Methods void postDirty ( InstanceLifecycleEvent  event) Invoked whenever a persistent instance is first made dirty

javax.jdo.listener.DetachLifecycleListener

JDO Interface DetachLifecycleListener Super Interfaces: InstanceLifecycleListener This interface is implemented by listeners to be notified of detach events. Since: JDO 2.0 Public Methods void postDetach ( InstanceLifecycleEvent  event) This method is called during the execution of javax.jdo

[ODB1] Chapter 5 - JDO Connections

is expected to be running on a machine named host (could be domain name or ip address) and listening ... (the same machine) and listening to the default port (6136): Properties properties = new Properties

javax.jdo.listener.StoreCallback

javax.jdo.listener.StoreCallback

javax.jdo.listener.LoadCallback

javax.jdo.listener.LoadCallback

javax.jdo.listener.DetachCallback

javax.jdo.listener.DetachCallback

javax.jdo.listener.DeleteCallback

javax.jdo.listener.DeleteCallback

javax.jdo.listener.ClearCallback

javax.jdo.listener.ClearCallback

javax.jdo.listener.AttachCallback

javax.jdo.listener.AttachCallback

javax.jdo.PersistenceManagerFactory

} ("manageMetadata") Since: JDO 2.2 void addInstanceLifecycleListener ( InstanceLifecycleListener   listener , Class[] classes) Add the parameter listener to the list of instance lifecycle event listeners set as the initial listeners for each PersistenceManager created by this PersistenceManagerFactory

javax.jdo.PersistenceManager

addInstanceLifecycleListener ( InstanceLifecycleListener   listener , Class... classes) Adds the listener instance to the list of lifecycle event listeners . The classes parameter identifies ... event for which it implements the corresponding listenerInstance interface. Parameters: listener

javax.jdo.spi.JDOImplHelper

to the listener list. Parameters: crl - the listener to be added Since: JDO 1.0 void addStateInterrogation ... removeRegisterClassListener ( RegisterClassListener  crl) Remove the specified RegisterClassListener from the listener list. Parameters: crl - the listener to be removed Since: JDO 1.0 void removeStateInterrogation