org.lsst.ccs.localdb.statusdb

Class StatusPersister

java.lang.Object

org.lsst.ccs.localdb.statusdb.BatchPersister<Object[]>

org.lsst.ccs.localdb.statusdb.StatusPersister

All Implemented Interfaces:

Runnable, org.lsst.ccs.framework.AlertHandler, org.lsst.ccs.framework.ClearAlertHandler, org.lsst.ccs.framework.HasLifecycle, org.lsst.ccs.messaging.AgentPresenceListener, org.lsst.ccs.messaging.MessageListener, org.lsst.ccs.messaging.StatusMessageListener

public class StatusPersister
extends BatchPersister<Object[]>
implements org.lsst.ccs.messaging.StatusMessageListener, org.lsst.ccs.messaging.AgentPresenceListener, org.lsst.ccs.framework.HasLifecycle

Author:

LSST CCS Team

Nested Class Summary

Nested classes/interfaces inherited from interface org.lsst.ccs.framework.ClearAlertHandler

org.lsst.ccs.framework.ClearAlertHandler.ClearAlertCode

Field Summary

Fields inherited from class org.lsst.ccs.localdb.statusdb.BatchPersister

alertService

Constructor Summary

Constructors

Constructor and Description
StatusPersister()

Method Summary

Modifier and Type	Method and Description
void	build()
void	connecting(org.lsst.ccs.bus.data.AgentInfo... agents) AgentPresenceListener callback methods.
void	disconnecting(org.lsst.ccs.bus.data.AgentInfo agent) The active alerts for the disconnecting agent are pushed to history.
void	onStatusMessage(org.lsst.ccs.bus.messages.StatusMessage msg)
void	persist(Object[] obj, Session sess) Called from inside a transaction.
void	start()

Methods inherited from class org.lsst.ccs.localdb.statusdb.BatchPersister

addToQueue, canClearAlert, run

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.lsst.ccs.messaging.AgentPresenceListener

connected

Methods inherited from interface org.lsst.ccs.framework.HasLifecycle

init, postBuild, postInit, postShutdown, postStart, shutdown

Methods inherited from interface org.lsst.ccs.framework.ClearAlertHandler

canClearAlert

Constructor Detail

StatusPersister

public StatusPersister()

Method Detail

build

public void build()

Specified by:

build in interface org.lsst.ccs.framework.HasLifecycle

start

public void start()

Specified by:

start in interface org.lsst.ccs.framework.HasLifecycle

onStatusMessage

public void onStatusMessage(org.lsst.ccs.bus.messages.StatusMessage msg)

Specified by:

onStatusMessage in interface org.lsst.ccs.messaging.StatusMessageListener

connecting

public void connecting(org.lsst.ccs.bus.data.AgentInfo... agents)

AgentPresenceListener callback methods. When a agent connects, its alert entries in ActiveRaisedAlertData are removed.

Specified by:

connecting in interface org.lsst.ccs.messaging.AgentPresenceListener

Parameters:

agent -

disconnecting

public void disconnecting(org.lsst.ccs.bus.data.AgentInfo agent)

The active alerts for the disconnecting agent are pushed to history.

Specified by:

disconnecting in interface org.lsst.ccs.messaging.AgentPresenceListener

Parameters:

agent -

persist

public void persist(Object[] obj,
                    Session sess)

Called from inside a transaction. This method is called sequentially : LocaldbFacade needs not be thread safe. TO-DO : is this the right strategy ?

Specified by:

persist in class BatchPersister<Object[]>

Parameters:

obj -

sess -