AssetPropertyDescriptor  - AS3 ADEP Content

Is property represented by this instance is extended property of the original asset/vo

Asset property type whether it is extended or core property

Is the basic search enabled on the property. There can be only one such property for each asset type.

Collection of child property descriptor of this property if it is composite type property.

display column order of the property in SRV

Fully qualified class name of custom Item renderer for dispaying this property in SRV. It should implement mx.core.IDataRenderer interface.

The display name of the property

Display pattern if the property is of type date.

Map of extended properties associated with this property

if this prperty is and extended VO property, then path of this property in actual VO.

Is the property to be fetched during Search. Normally cutpoints are created from visible or reviewable properties whose searchType is of the form A.B.C so as to avoid duplicate cutpoints. This is to be used in case some other property which is not searchable or reviewable but still is to be fetched from the server.

Maximum property value. valid for Numeric properties

Minimum property value. valid for Numeric properties

name of the asset property

Option list of data-label pairs.

path of the asset property

DD Property type whether this is coposite property or simple property

Is the property to be shown in Properties Panel

Is the property searchable

The path of the property used in search queries. If this empty then "path" is used as searchPath

Fully qualified name for the custom search renderer of the property. The class should extend com.adobe.livecycle.ria.assetmanager.view.components.search.ISearchUIControl

Order of the search renderer of this property in search pod.

Is the property visible in SRV(Search Results Viewer Pod)

Constructor.

Registers an event listener object with an EventDispatcher object so that the listener receives notification of an event. You can register event listeners on all nodes in the display list for a specific type of event, phase, and priority.

After you successfully register an event listener, you cannot change its priority through additional calls to addEventListener(). To change a listener's priority, you must first call removeEventListener(). Then you can register the listener again with the new priority level.

After the listener is registered, subsequent calls to addEventListener() with a different value for either type or useCapture result in the creation of a separate listener registration. For example, if you first register a listener with useCapture set to true, it listens only during the capture phase. If you call addEventListener() again using the same listener object, but with useCapture set to false, you have two separate listeners: one that listens during the capture phase, and another that listens during the target and bubbling phases.

You cannot register an event listener for only the target phase or the bubbling phase. Those phases are coupled during registration because bubbling applies only to the ancestors of the target node.

When you no longer need an event listener, remove it by calling EventDispatcher.removeEventListener(); otherwise, memory problems might result. Objects with registered event listeners are not automatically removed from memory because the garbage collector does not remove objects that still have references.

Copying an EventDispatcher instance does not copy the event listeners attached to it. (If your newly created node needs an event listener, you must attach the listener after creating the node.) However, if you move an EventDispatcher instance, the event listeners attached to it move along with it.

If the event listener is being registered on a node while an event is also being processed on this node, the event listener is not triggered during the current phase but may be triggered during a later phase in the event flow, such as the bubbling phase.

If an event listener is removed from a node while an event is being processed on the node, it is still triggered by the current actions. After it is removed, the event listener is never invoked again (unless it is registered again for future processing).

Parameters

Dispatches an event into the event flow. The event target is the EventDispatcher object upon which dispatchEvent() is called.

Parameters

Checks whether the EventDispatcher object has any listeners registered for a specific type of event. This allows you to determine where an EventDispatcher object has altered handling of an event type in the event flow hierarchy. To determine whether a specific event type will actually trigger an event listener, use IEventDispatcher.willTrigger().

The difference between hasEventListener() and willTrigger() is that hasEventListener() examines only the object to which it belongs, whereas willTrigger() examines the entire event flow for the event specified by the type parameter.

Parameters

Method to check whether this property is a composite property that have child properties or not.

Removes a listener from the EventDispatcher object. If there is no matching listener registered with the EventDispatcher object, a call to this method has no effect.

Parameters

Checks whether an event listener is registered with this EventDispatcher object or any of its ancestors for the specified event type. This method returns true if an event listener is triggered during any phase of the event flow when an event of the specified type is dispatched to this EventDispatcher object or any of its descendants.

The difference between hasEventListener() and willTrigger() is that hasEventListener() examines only the object to which it belongs, whereas willTrigger() examines the entire event flow for the event specified by the type parameter.

Parameters

This special value signifies that the property defined is an extended property