Wildcard characters can be used in topic expressions to retrieve topics provided by the default messaging provider and service integration technologies.
Each subscribe request includes a topic expression that identifies one or more topics that the subscription is to be associated with, and that the request uses to match against incoming messages.
Subscription topic expressions for the default messaging provider and service integration technologies are based on a subset of the XPath location path syntax.
Topic name = name_part | (name_part '/' topic_name)
To select one or more topics in a topic space, you can use a topic path, a location path that contains wildcard characters. Topic spaces are evaluated by using a subset of the XPath location path syntax with the <topicspace> element as the initial context node, so that non-wildcarded topic paths look exactly like topic names.
A * can be used anywhere in a topic path expression, but if it isn't at the start it must be preceded by a /, and if it is isn't at the end it must be followed by a /
A // can be used anywhere in the expression except at the end. To match 0 or more levels at the end of the expression you end the expression with the syntax //. (double-slash dot). To match one or more levels at the end use //* (double-slash asterisk)
A topic path must not contain more than two consecutive / symbols.
Topic path | Topics selected | WBI Message Broker equivalent |
A/B | Selects the B child of A | A/B |
A/* | Selects all children of A | A/+ |
A//* | Selects all descendents of A | A/#/+ |
A//. | Selects A and all descendents of A | A/# |
//* | Selects everything | # (or #/+) |
A/./B | Equivalent to A/B | A/B |
A/*/B | Selects all B grandchildren of A | A/+/B |
A//B | Selects all B descendents of A | A/#/B |
//A | Selects all A elements at any level | #/A |
* | Selects all first level elements | + |
Existing WebSphere® Application Server Version 5.1 client applications using Version 5.1 connection factory and destination definitions use the WBI Message Broker wildcard convention. Such applications can connect to the default messaging provider and service integration bus, and automatically have their wildcard syntax mapped to the XPath convention when subscriptions are created. Any display of these subscriptions through an administrative interface to the bus shows the XPath syntax.