Root element for the log file. The scope of the log file
is a single end point.
Meta-data about the log file such as the time created,
what tool and version was used to create the log,
environment used, runtime, operating system, etc.
Used to identify a message. This represents a message
moving in one direction.
Identifies the entry as an HTTP request or an HTTP
response. Valid values are request and response.
This attribute is used to uniquely identify the message
within the log.
In the case of http, it must uniquely identify each http
transaction (request/response pair). This identifier is
used to group messages received between the time that
the client connects to the monitor port and when that
connection is closed. The string MUST change in between
connections.
Contains the HTTP Body message in the HTTP POST or HTTP
response.
This is for cases when the logger could not capture
the message since it was invalid XML.
Note that the actual element to log is determined by the
Content-Type HTTP header field-value. If the field-value
has a media-type of "multipart/related", then the
"messageContentWithAttachments" element is logged.
Otherwise, the "messageContent" element is always
logged.
A root or non-root part of a multipart/related message.
This identifies the boundary string delimiter
including the preceding ascii characters that separate
the part boundary.
A standardized set of headers that describe the
structure and content of a MIME part.
The description files for the service such as the WSDL
and XSD.
For BP, this is either a WSDL description or XSD
schema.
This is for cases when the logger could not capture the
description file since it was invalid XML.
The filename and the extension (.wsdl or .xsd).
Enumerates the possible @mode values for a feature.
Describes an advertised feature/requirement of the described endpoint.