Why does the File Adapter have wire and native classes?
Article ID: KB0088981
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Files for Unix and Windows | - |
| Not Applicable | - |
Description
Resolution:
The File Adapter palette will create a wire class and native class for every File Record. These classes exist purely to separate adapter specific information and information that can be shared with other adapters.
The native class exists to capture information related to parsing and formatting. This information is specific to the file adapter and should not be shared with other adapters.
The wire class allows the file adapter to share the structure of the data file and the data file itself with the other adapters.
The native class holds metadata about the attributes defined in the wire class; for scalar attributes, the mapping is one to one.
When a parent child relationship exists, the wire class will have the sequence for each of the children while the native class will have an association with each of the children.
The File Adapter palette will create a wire class and native class for every File Record. These classes exist purely to separate adapter specific information and information that can be shared with other adapters.
The native class exists to capture information related to parsing and formatting. This information is specific to the file adapter and should not be shared with other adapters.
The wire class allows the file adapter to share the structure of the data file and the data file itself with the other adapters.
The native class holds metadata about the attributes defined in the wire class; for scalar attributes, the mapping is one to one.
When a parent child relationship exists, the wire class will have the sequence for each of the children while the native class will have an association with each of the children.
Issue/Introduction
Why does the File Adapter have wire and native classes?
Feedback
Yes
No
Powered by
