can't open a receiver bound to application header x-match expression

I’m trying to adapt https://github.com/amqp/rhea/tree/master/examples/selector example using an x-match expression instead of a JMS expression. Tried this code:

connection.open_receiver({
	source: {
		address: 'amq.match',
		filter: {
			'x-match': 'all',
			value: {
				'nat': 'it',
				'prod': 'a22'
			}
		}
	}
})

Received “connection_error Expected value type is ‘Filter’ but got ‘String’ amqp:decode-error” from Qpidd Java broker (rel. 7.1.0).

[k-wall]

@k-wall I tried JMS filters (example here on rhea repo) and they work fine with Qpid Broker-J but using “amq.topic” exchange instead of “amq.match” (so strange)

@beaver71 The exchange concept comes from the old pre-AMQP 1.0 world (AMQP 0-x). It was those specifications that defined the behaviour of how instances of the in-built exchange types worked. amq.match (which is an instance of the “header” exchange type) was never defined as understanding message selectors. The exchange concept does not exist in AMQP 1.0 so you won’t find the concept in other AMQP providers. Apache Qpid did this to help is legacy user move to the new world.

I generally encourage message users to utilise standard messaging features when building their applications. So I echo @grs comments to use message selectors if you can for your use-case.

[grs]

This works with the qpid c++ broker:

var container = require('rhea');
var types = require('rhea').types;

var args = require('../options.js').options({
    'h': { alias: 'host', default: 'localhost', describe: 'dns or ip name of server where you want to connect'},
    'p': { alias: 'port', default: 5672, describe: 'port to connect to'}
}).help('help').argv;

container.on('message', function (context) {
    console.log(context.message.body);
});

container.once('sendable', function (context) {
    context.sender.send({application_properties:{'a': 'foo', 'b': 'bar'}, body:'first matches'});
    context.sender.send({application_properties:{'y': 'foo', 'b': 'bar'}, body:'second does not match'});
    context.sender.send({application_properties:{'a': 'foo', 'b': 'bar', 'x':'y'}, body:'third matches'});
    context.sender.send({application_properties:{'a': 'foox', 'bx': 'bar'}, body:'fourth does not match'});
});

var con = container.connect({ port: args.port, host: args.host });
con.open_receiver({source:{address:'amq.match', filter:{'foo':types.wrap_described({'a': 'foo', 'b': 'bar', 'x-match': 'all'}, 0x468C00000002)}}});
con.open_sender({target:{address:'amq.match'}});

ActiveMQ does not support the headers exchange or this particular filter. The qpid java broker does support the headers exchange but I am not sure if it supports this filter definition. I’ll try and find out - certainly the code above does not work against that broker.