![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The SDK parses metadata objects found in the project repository and populates the class registry. By default, this happens upon startup.
It is recommended to have all metadata data parsed upon startup. See Adapter Metadata Look-up for instructions on how to alter this behavior.
• MModeledClassDescription encapsulates the descriptions of the classes themselves. It describes MInstance.
• MSequenceClassDescription encapsulates attribute types that are sequences. It describes MSequence.
• MOperationParameterDescription encapsulates operation parameters. It describes the expected inputs and outputs for an ActiveEnterprise operation.
• In the C++ SDK, MPrimitiveClassDescription encapsulates simple attribute type descriptions. It governs such classes as MInteger, MBinary, or MReal. (The Java SDK uses Java native classes in this case).When the SDK reads the metadata from the adapter instance in the repository, each attribute must have a name and type. The SDK creates an MAttributeDescription for each attribute. Custom adapters can then set the attributes when they send the information over the wire. Custom adapters can also access the following information.
Assume you have created an Order class with four attributes. Three of the attributes are strings, the other, Orderlines, is a sequence of four attributes.In this case, MApp would generate one MModeledClassDescription with four associated MAttributeDescription instances for the Order class, as well as one MModeledClassDescription with four associated MAttributeDescription instances for the OrderLine class. MApp also creates an MSequenceClassDescription consisting of one or more OrderLine instances.
Table 25 Metadata Hierarchy Example Order class MModeledClassDescription with four associated MAttributeDescription classes. Order/ Orderlines attribute OrderLine class MModeledClassDescription with four associated MAttributeDescription classes.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |