Справочник Пользователя для IBM WebSphere Adapters
Data and metadata
Adapter Foundation Classes (AFC) implement DESPI APIs and support two data
formats, service data objects (SDO) and JavaBeans.
formats, service data objects (SDO) and JavaBeans.
The data format-specific implementations are provided in the AFC and are
abstracted from the adapters which use the DESPI APIs to process data in a
format-independent way.
abstracted from the adapters which use the DESPI APIs to process data in a
format-independent way.
XSD and JavaBean structure relationship to DESPI
SDO Structure:
JavaBeanRecord Structure:
The JavaBeanRecord data structure is derived from the XML Schema defining the
SDO. Adapter foundation classes provide an implementation of RecordGenerator
which generates JavaBeanRecords for a given SDO/XML Schema.
SDO. Adapter foundation classes provide an implementation of RecordGenerator
which generates JavaBeanRecords for a given SDO/XML Schema.
The RecordGenerator class is used by the adapter enterprise metadata to generate
the required artifacts for Java Bean Record data format. See Enterprise metadata
implementation details on how to update the adapter enterprise metadata (EMD)
implementation to use the RecordGenerator class.
the required artifacts for Java Bean Record data format. See Enterprise metadata
implementation details on how to update the adapter enterprise metadata (EMD)
implementation to use the RecordGenerator class.
Type mappings: Bean properties map to the attributes of a given complex type. The
types of the simple attributes are derived from the XML built-in data types defined
in the input schema for each subelement of the complex type. The sub-elements
containing n-cardinality child objects are always defined as an array of the child
type while single cardinality sub-elements are represented as a JavaBean property
with the type of the subelement.
types of the simple attributes are derived from the XML built-in data types defined
in the input schema for each subelement of the complex type. The sub-elements
containing n-cardinality child objects are always defined as an array of the child
type while single cardinality sub-elements are represented as a JavaBean property
with the type of the subelement.
The following is a table showing the mapping between the built-in XML Schema
Definition (XSD) types and bean properties generated by the RecordGenerator
implementation in the AFC.
Definition (XSD) types and bean properties generated by the RecordGenerator
implementation in the AFC.
Table 2. Mapping between built-in XSD schema and JavaBean properties
Header
Header
Boolean
boolean
String
String
Int
int
Integer
Integer
Decimal
BigDecimal
Double
double
Float
float
Long
long
Short
short
hexBinary
byte[] (byte array)
Byte
byte
dateTime
Calendar
Date
Calendar
Time
Calendar
WebSphere Adapter development overview
115