OSS Java complexType EntitySpecificationValue

Type Heirarchy
{http://java.sun.com/products/oss/xml/Common}ManagedEntityValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Core}CBEManagedEntityValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Core}EntitySpecificationValue

Derived Types
{http://java.sun.com/products/oss/xml/CBE/Core}EntitySpecificationValue {http://java.sun.com/products/oss/xml/CBE/Product}ProductSpecificationValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Service}ServiceSpecificationValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Sla}SLAItemSpecificationValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Sla}SLASpecificationValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Resource}ResourceSpecificationValue (by extension) {http://java.sun.com/products/oss/xml/CBE/Product/ProductOffering}ProductOfferingValue (by extension)

Abstract	false (This can be used in an instance)
Target Namespace	http://java.sun.com/products/oss/xml/CBE/Core
Declared Namespaces	xmlns:cbecore=http://java.sun.com/products/oss/xml/CBE/Core xmlns:co=http://java.sun.com/products/oss/xml/Common xmlns=http://www.w3.org/2001/XMLSchema

<complexType name="EntitySpecificationValue">
 <annotation>
 <documentation>
<CODE>EntitySpecificationValue</CODE> is the base for all specification entities.

An entity specification captures characteristics and constraints
applicable to instances of the same entity type. For example a
"<CODE>GoldBroadbandAccessServicespecification</CODE>" will capture the characteristics,
configuration and QoS parameter ranges, specific to a "<CODE>Gold</CODE>" Broadband
Access service offering. Several specification instances may exist for the same
entity type. "<CODE>Gold</CODE>", "<CODE>Silver</CODE>" and "<CODE>Bronze</CODE>" specifications may be defined
for a "<CODE>BroadbandAccessService</CODE>".

Catalogues are collections of entity specifications (e.g. service catalogue composed
of service specifications, product catalogue composed of product specifications, resource
catalogue composed of resource specifications).

An entity instance is defined by a single entity specification.
The same entity specification may be used to define multiple entity instances.
An association exists between the entity specification and the entity instances,
defined by this specification (the values of the <CODE>describingSpecification</CODE>
attributes of the entities are set with the key of the specification).
The specification defines default values for all attributes of the corresponding entity type.

Entity specifications provide a factory method for the attribute constraints they contain.
Note that the CBE package does not specify through how attribute constraints are defined.
Specific implementations of the CBE interfaces should define the
concrete attribute constraint interfaces and the methods on the entity specification
that allow to get and set these constraints.

Entity specifications are represented as managed entities
(according to the OSS through Java definition of managed entity).
<CODE>EntitySpecification</CODE> instances have their own key and can be retrieved through
API specific <CODE>JVTSession</CODE> interfaces.
The following example show how to use the Inventory API to update a <CODE>ProductSpecification</CODE>:
<pre>
<CODE>
JVTInventorySession jvt = ...;
EntitySpecificationKey key = ...;
ProductSpecificationValue value = (ProductSpecificationValue)jvt.getEntitySpecificationByKey(key);
value.setAttributeValue("...");
jvt.setEntitySpecificationByValue(value);
</CODE>
</pre>

The specification for a given entity type may be used as a factory for
value objects or for creating entity instances of this entity type.
For example using the Inventory API:
<pre>
<CODE>JVT<...>InventorySession.make<...>EntityValueFromSpecification()</CODE> and the
<CODE>JVT<...>InventorySession.create<...>EntityFromSpecification()</CODE> methods.
</pre>

Entity specifications are uniquely identified by their keys.
See {@link EntitySpecificationKey} for more information.

<CODE>EntitySpecificationValue</CODE> inherits from <CODE>ManagedEntityValue</CODE> all methods
for population, generic attribute access and serialization.
 </documentation>
 </annotation>
 <complexContent>
 <extension base="cbecore:CBEManagedEntityValue">
 <sequence>
 <element name="describedEntityType" minOccurs="0" nillable="true" type="string"/>
 </sequence>
 </extension>
 </complexContent>
</complexType>

An entity specification captures characteristics and constraints applicable to instances of the same entity type. For example a "GoldBroadbandAccessServicespecification" will capture the characteristics, configuration and QoS parameter ranges, specific to a "Gold" Broadband Access service offering. Several specification instances may exist for the same entity type. "Gold", "Silver" and "Bronze" specifications may be defined for a "BroadbandAccessService".

Catalogues are collections of entity specifications (e.g. service catalogue composed of service specifications, product catalogue composed of product specifications, resource catalogue composed of resource specifications).

An entity instance is defined by a single entity specification. The same entity specification may be used to define multiple entity instances. An association exists between the entity specification and the entity instances, defined by this specification (the values of the describingSpecification attributes of the entities are set with the key of the specification). The specification defines default values for all attributes of the corresponding entity type.

Entity specifications provide a factory method for the attribute constraints they contain. Note that the CBE package does not specify through how attribute constraints are defined. Specific implementations of the CBE interfaces should define the concrete attribute constraint interfaces and the methods on the entity specification that allow to get and set these constraints.

Entity specifications are represented as managed entities (according to the OSS through Java definition of managed entity). EntitySpecification instances have their own key and can be retrieved through API specific JVTSession interfaces. The following example show how to use the Inventory API to update a ProductSpecification:

The specification for a given entity type may be used as a factory for value objects or for creating entity instances of this entity type. For example using the Inventory API:

Entity specifications are uniquely identified by their keys. See {@link EntitySpecificationKey} for more information.

EntitySpecificationValue inherits from ManagedEntityValue all methods for population, generic attribute access and serialization.

complexType {http://java.sun.com/products/oss/xml/CBE/Core}EntitySpecificationValue

Source

Documentation