Static queues and topics are assigned certain properties in the configuration file. These static queues and topics become the parents of dynamic queues and topics, which inherit properties from the parents. You must understand wildcards to understand the inheritance rules.
To understand the rules for inheritance of properties, it is important to understand the use of the two wildcards, *
and >
.
*
means that any token can be in the place of *
For example: foo.
* matches all two-part destination names beginning with foo
. including foo.bar
and foo.boo
, but not foo.bar.boo
.
However, foo.
*.bar
matches all three-part destination names with a token in the wildcard position. In this case, foo.boo.bar
is matched, but foo.bar
is not.
>
matches one or more trailing elements.
For example, foo.>
matches foo.bar
and foo.bar.boo
TIBCO Enterprise Message Service enables you to use wildcards in topic names in some situations:
If you subscribe to a topic containing a wildcard, you will receive any message published to a matching topic. For example, if you subscribe to foo.*
you will receive messages published to a topic named foo.bar
.
You can subscribe to a wildcard topic (for example foo.
*), whether or not there is a matching topic in the configuration file (for example, foo.
*, foo.>
, or foo.bar
). However, if there is no matching topic name in the configuration file, no messages will be published on that topic, so it is not useful to subscribe to the wildcard topic in that case.
foo.bar
is not in the configuration file, then you can publish to foo.bar
if foo.*
or foo.>
exists in the configuration file. TIBCO Enterprise Message Service enables you to use wildcards in queue names in some situations. You can not send or receive to wildcard queue names. However, you can use wildcard queue names in the configuration files. The wildcard queue names in the configuration files must have non-wildcard children to send and receive messages.
For example, if the queue configuration file includes a line:
then users can create queues foo.bar
, foo.bob
, and so forth, but not foo.bar.bob
.
TIBCO Enterprise Message Service™ User’s Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |