Open topic with navigation

# JMS Message Types

TIBCO FTL uses only one type of message - unlike JMS, which uses several message types. Yet you can use FTL messages to emulate most of the JMS message types.

The structure of an FTL message is analogous to that of a JMS MapMessage. Other JMS message types are either conveniences or optimizations.

To emulate JMS message types, use the FTL equivalents in the following table.

JMS | FTL
--- | ---
Message A message without a body, for event notification. | Include only those fields that are required for content-based addressing.
TextMessage A message containing only a string. | Include one field, with a string value.
MapMessage A set of name/value pairs. | Include all the name/value pairs as fields.
BytesMessage A stream of bytes. | Include one opaque field with the bytes as its value. For optimized performance use either the opaque or keyed opaque built-in formats.
StreamMessage | No direct equivalent in TIBCO FTL. Encode within an opaque.
ObjectMessage | No direct equivalent in TIBCO FTL.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.