Indicates objects that are dependent.

A DependentObject represents an EngineObject that can only exist within the scope of another object. An example of this dependency is ContentElement; content elements are scoped to a particular Document object and cannot exist independently. Contrast this with an IndependentObject, which is an EngineObject that has its own independent identity.

The identity and security of a dependent object are derived from that of its parent independent object.

DependentObjects and DependentObjectLists are not reusable. That is, a DependentObject or DependentObjectList taken from a fetched object should not be reassigned to another object. Once they have been assigned to one parent object, they must not be assigned to a second parent object. For example, you should not fetch the Permission obects for one object and then try to directly use those same Permission objects on another object. If you attempt such reuse, the results are unpredictable. In some cases, there may be no adverse effects. The operation might appear to succeed but give results other than what the caller expects, for example, errors when you try to save the object. In other cases, the attempted operation might fail with symptoms that are difficult to diagnose.

Any attempt to assign an already-assigned DependentObject to another parent object causes a warning message to be written to the client trace log.

Note: While this type of operation might succeed with the 4.0 Content Engine API, the behavior is unreliable and future releases of the Content Engine API will prohibit reuse by throwing a runtime exception.


Namespace: FileNet.Api.Core
Assembly: FileNet.Api (in filenet.api.dll)

Syntax

Visual Basic (Declaration)
Public Interface IDependentObject
C#
public interface IDependentObject
C++
interface class IDependentObject
J#
public interface IDependentObject
JScript
public interface IDependentObject

See Also