Resolution:
No, neither SDK 4 nor 5 support TibrvMsg.XML; but, SDK 5.0.1 and onward
allow developers to integrate with systems that primarily understand XML
documents and XML Schemas. The Adapter SDK 5 provide support for XML
such that users can retrieve their data as XML documents and their metadata
as XML Schemas (XSD). Users are able to select XML as the wireformat for
both JMS and RV transport on a per-endpoint basis.

If the TibrvMsg.XML data compression feature is *absolutely* necessary,
you can use the MTree.append() method.  Please note that MTree doesn't
provide direct support for appending TIBRVMSG_XML type data, however,
user can still use the internal Java SDK method (**NOTE**: Interal methods
are not supported by TIBCO, hence their usage is not recommended, and
they are not garranteed to remain the same in future releases).  And it will
be a straight pass thru to RV.

Then, use MPublisher.send(MTree) to send your message.  This way, you
can still use repo configuration to configure his publisher/subscriber
and at the same time use TIBRVMSG feature that is not available in SDK.
When needed, user can/should use direct RV API, however minimizing direct
RV API call help retaining benefits of SDK features.

With SDK 4.1.x, if you wish to send XML format text (message) from Adapter
build with TIBCO Adapter SDK, simply append the text into a string type field
of a MInstance and serialize for transmission.