Package com.sas.metadata.remote

Interface SecondaryType

All Superinterfaces:
CMetadata, MdObjectBase, MdObjectBaseUtil, MdObjectBaseXML, Remote, Root
All Known Subinterfaces:
AbstractExtension, AbstractProperty, AnalyticColumn, AnalyticTable, AssociationProperty, AttributeProperty, Change, ConditionalPrecedence, CustomAssociation, Extension, ExternalIdentity, FitStatistic, ForeignKey, GroupByClause, HavingClause, InternalLogin, ITFilter, Key, KeyAssociation, Keyword, LocalizedResource, LocalizedType, Location, NumericExtension, OnClause, OrderByClause, PermissionCondition, Phone, Property, PropertyGroup, PropertySet, PropertyType, PrototypeProperty, QueryClause, ResponsibleParty, Role, RowSelector, SASPassword, SecurityRule, SecurityTypeContainmentRule, ServiceType, StepPrecedence, Target, Timestamp, UniqueKey, UnitofTime, Variable, WhereClause, XPath
public interface SecondaryType extends Root
The SecondaryType subtypes are used along with the PrimaryType subtypes to create a logical metadata definition for an object. The SecondaryType subtypes provide supporting information in the logical metadata definition.

SecondaryType subtypes may not reside in a folder and are contained, directly or indirectly, by a PrimaryType subtype. SecondaryType objects may not be shared between logical metadata definitions.

Attributes of SecondaryType are:

Associations of SecondaryType are:

Usage

To create an instance of this SecondaryType, use the factory create methods.
Example: create a SecondaryType with name "SecondaryType_Object", in repository "AAAAAAAA".
 // create a store to contain your objects for this change. If you do not have an existing object
 // or store to use.  You may obtain the store from another object by using Object.getObjectStore().
 MdFactory factory; //where "factory" is a valid MdFactory instance
 MdObjectStore objectStore = factory.createObjectStore();
 SecondaryType myObject = (SecondaryType) factory.createComplexMetadataObject(objectStore, "SecondaryType_Object", MetadataObjects.SECONDARYTYPE, "AAAAAAAA");
 myObject.updateMetadataAll();  // Write object to server
 objectStore.dispose();  // dispose of the object store if it is no longer needed

Behavior

  • Attributes and associations for this object can be retrieved by using the methods in MdOMIUtil.
  • When changes are made to the object, either by setting an attribute or adding objects to a particular association, they can be persisted to the metadata server with the updateMetadataAll method.
  • If an object needs to be deleted, the delete method can be used. This will flag the object as being deleted on the client, and will require an update call to persist the change to the server.

Dependencies

This class depends on objects being contained in an MdObjectStore. Object stores should be disposed of when they are no longer needed as this will help clean up memory. Disposing an object store will dispose of all objects contained within that store.

Since:
9.0

  • Method Details

    • initializeRequiredObjects

      void initializeRequiredObjects() throws RemoteException
      (S) This initializes the Required Objects(Roles) which are:
      Specified by:
      initializeRequiredObjects in interface MdObjectBaseUtil
      Specified by:
      initializeRequiredObjects in interface Root
      Throws:
      RemoteException - If error connecting/communicating to/with remote object.

    • initializePredObjects

      void initializePredObjects() throws RemoteException
      (S) Adds the Associated objects to the predObjects which are:
      Specified by:
      initializePredObjects in interface MdObjectBase
      Specified by:
      initializePredObjects in interface Root
      Throws:
      RemoteException - If error connecting/communicating to/with remote object.