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}AssociationValue

Derived Types

{http://java.sun.com/products/oss/xml/CBE/Core}AssociationValue  {http://java.sun.com/products/oss/xml/CBE/Cross}CrossAssociationValue (by extension)  {http://java.sun.com/products/oss/xml/CBE/Service}ServiceAssociationValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Service}ServiceAggregatesServiceAssocValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Service}ServiceSpecificationAggregatesServiceSpecificationAssocValue (by extension)  {http://java.sun.com/products/oss/xml/CBE/Product}ProductAssociationValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Product}ProductSpecificationAggregatesProductSpecificationAssocValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Product}ProductAggregatesProductAssocValue (by extension)  {http://java.sun.com/products/oss/xml/CBE/Resource}ResourceAssociationValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Resource}ResourceAggregatesResourceAssocValue (by extension)   {http://java.sun.com/products/oss/xml/CBE/Resource}ResourceSpecificationAggregatesResourceSpecificationAssocValue (by extension)

The <CODE>AssociationValue</CODE>  is the base from which all association
  interfaces are derived.
 <p>
 Associations are represented in the CBE package as managed entities
 (according to the OSS through Java definition of managed entity).
 <CODE>Association</CODE> instances have their own keys.
 <p>
 The following attributes of an <CODE>AssociationValue</CODE> are set at creation:
 <ul>
 <li>EntityKey
 <li>the key of object A (A end)
 <li>the key of object Z (Z end)
 </ul>
 Note that other attributes could be defined by concrete association values
 derived from this base interface. However these attributes should be specific
 to this association and should not depend on the state of other objects.
 <p>
 The roles are captured in the definition of the association attributes
 and in the corresponding {@link AssociationRule AssociationRule}.
 For example in a "<CODE>SupportedBy</CODE>" type of association for one of the
 objects will be defined an attribute "<CODE>supporting</CODE>" and "<CODE>supported</CODE>" for the other.
 The corresponding <CODE>AssociationRule</CODE> will define the A and Z end roles as
 "<CODE>supporting</CODE>" and "<CODE>supported</CODE>".
 <p>
 An {@link AssociationRule AssociationRule} is provided for every concrete
 association type. The rule defines the constraints for this association type
 (e.g. roles, cardinality, association constraints).
 <p>
 Associations are uniquely identified by their keys.
 See {@link AssociationKey AssociationKey}
 for more information.
 <p>
 The <CODE>AssociationValue</CODE> inherits from <CODE>ManagedEntityValue</CODE> all methods
 for population, generic attribute access and serialization.

Stylus Studio XML Schema Library Home

Site Map | Privacy Policy | Terms of Use | Trademarks

Stylus Scoop XML Newsletter:

Stylus Studio®, a product from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2006 All Rights Reserved.