====== Containerizer Types ====== ^Name^Description^ |**eBiss.ClassLib.Containerizers.AnsiX12Containerizer**|When creating custom AnsiX12 messages, the namespace must end with: .V.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 files((usually eBiss MiddleWare types)) with an interchange, so that the partner identification remains transparent in case of a [[en:howtos:multiknotenkommunikation|Internodecommunication]]((Provided that the partners have a appropriate **DEFAULT Interchange Address** (See [[en:partnerverwaltung:kommunikation:adresseanlegen#adresstypen|Address types]]).)).| |**eBiss.ClassLib.Containerizers.PlainContainerizer**|The PlainContainerizer should usually be used if no specific modification is required during containerization.| |eBiss.ClassLib.Containerizers.XMLContainerizer|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**|FIXME | |**eBiss.Tradacoms.TradacomsContainerizer**|FIXME | {{:images:sign_warning.png?nolink|}}**Note:** The **PlainContainerizer** is used to containerize XML.