Limitations of FioranoMQ Content Based Routing

Given below are a few of the known limitations of FioranoMQ Content Based Routing:

1. If an attribute or a tag does not exist and a message selector attempts to check the presence of that attribute or tag, then the message is not selected, irrespective of the nature of the selector. For instance, consider the following XML as an example:

   A message selector in the following form will return a 'false':
   
//Stock quotes/Symbol/AskPrice[@att1='0']=33.50
//Stock quotes/Symbol/AskPrice[@att1<>'0']=33.50
   
   This is because no attribute by the name 'att1' exists in the XML message and the message is not delivered.
   
   

   Similarly, a selector in the following form will return a 'false' and the message will not be delivered:
   
   //Stock quotes/Symbol/BidPrice<>212
   
   

2. 'Between' is not supported in attributes. It is, however, supported tags.

   Consider the XML given below:

   A selector in the following form is not supported;

   /Stock quotes/Symbol/AskPrice[@att1 between '12' and '13']:

   However, a selector in the following form is supported:

   /Stock quotes/Symbol/AskPrice between 30 and 40
 

3. Message selectors involving mathematical operations are not supported. For example, consider the XML given below:

   A message selector in the following form is not supported:

   /Stock quotes/Symbol/AskPrice = 0.3350*100

    

4. JMS message selectors in the following 'type' are not allowed:
   
   Consider a TextMessage on which the following properties have been set:

   
   A message selector in the following form is not supported:
   
mid_val between low_val and high_val