com.opencloud.util

Class AbstractDataObject

java.lang.Object

com.opencloud.util.AbstractDataObject

All Implemented Interfaces:

DataObject, Serializable

Direct Known Subclasses:

AbstractFieldsObject, BitString, SccpAddress

public abstract class AbstractDataObject
extends Object
implements DataObject

Simple base implementation of DataObject for cases where there's no other inheritance structure to get in the way.

See Also:

Serialized Form

Constructor Summary

Constructors

Constructor and Description
AbstractDataObject()

Method Summary

Methods

Modifier and Type	Method and Description
protected void	checkModify() Checks whether this DataObject is mutable.
abstract Object	clone() Perform a deep copy of this object.
boolean	isReadOnly() Check if this object has been set read-only.
void	setReadOnly() Set this object to be "read-only".

Methods inherited from class java.lang.Object

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

Constructor Detail

AbstractDataObject

public AbstractDataObject()

Method Detail

clone

public abstract Object clone()

Description copied from interface: DataObject

Perform a deep copy of this object. Read-only state of the object is not copied; the new object will be read-write by default.

Inherently immutable objects may optionally return the same object without modification from clone(), rather than constructing a new instance.

Specified by:

clone in interface DataObject

Overrides:

clone in class Object

Returns:

a new object that is a deep copy of this object; for immutable objects, the same object may optionally be returned.

setReadOnly

public void setReadOnly()

Description copied from interface: DataObject

Set this object to be "read-only". Any subsequent attempt to modify this object will throw IllegalStateException. Once an object has been made read-only, it cannot be later set to read-write - this is a "one-way" operation.

Note that a read-only object is not necessarily immutable; if reference types are returned from accessors, then callers could theoretically mutate those objects even if the top-level object is marked as read-only. The ability to make objects read-only is intended to catch programming errors (e.g. attempting to modify a data object passed as part of a SLEE event), not to provide an absolute guarantee of immutability.

Calling setReadOnly() on an object that is already read-only is a no-op.

Some DataObject implementations may be inherently immutable. In those cases, they are considered always read-only.

Specified by:

setReadOnly in interface DataObject

isReadOnly

public boolean isReadOnly()

Description copied from interface: DataObject

Check if this object has been set read-only.

Specified by:

isReadOnly in interface DataObject

Returns:

true if the object is read-only or inherently immutable

See Also:

DataObject.setReadOnly()

checkModify

protected void checkModify()

Checks whether this DataObject is mutable.

Throws:

IllegalStateException - if this DataObject is read-only