Containerizer Types
| Name | Description |
|---|---|
| eBiss.ClassLib.Containerizers.AnsiX12Containerizer | When creating custom AnsiX12 messages, the namespace must end with: .V<version number>.Messages. E.g. MyAnsiX12.V004010.Messages, the version number is generated in the GS segment of the message as well as the first two letters of the message type. |
| eBiss.ClassLib.Containerizers.AnsiX12ContainerizerEx | Like the AnsiX12Containerizer with the addition that partially filled GS segments are added to the unoccupied fields. |
| eBiss.ClassLib.Containerizers.EdifactContainerizer | The EdifactContainerizer can connect different UNHs to one file. |
| eBiss.ClassLib.Containerizers.InternalXmlContainerizer | The InternalXmlContainerizer is only used to enrich XML files1) with an interchange, so that the partner identification remains transparent in case of a Internodecommunication2). |
| eBiss.ClassLib.Containerizers.PlainContainerizer | The PlainContainerizer should usually be used if no specific modification is required during containerization. |
| Obsolete, please do not use any more. | |
| eBiss.ClassLib.Containerizers.XMLContainerizerEx | The XMLContainerizerEx can combine different XML with an interchange envelope to an XML document. |
| eBiss.ClassLib.Containerizers.XMLTexWeaveContainerizer |  |
| eBiss.Tradacoms.TradacomsContainerizer | |
Note: The PlainContainerizer is used to containerize XML.
1)
usually eBiss MiddleWare types
2)
Provided that the partners have a appropriate DEFAULT Interchange Address (See Address types).