Hi Adrian
As per current design guidelines, it is possible to register an event listener for only a subset of the message content. The guideline gives an example of setting up a selective listener for trouble ticket state changes, for only
urgent tickets, as follows:
POST /api/hub/
Accept: application/json
{
"callback": http://in.listener.com,
"query":"eventType = TroubleTicketStateChangeNotification & event.troubletTicket.severity=Urgent",
"fields":"event.troubleTicket.id, event.TroubleTicket.name, event.troubleTicket.severity"
}
Regarding the message content, look in the specification document for each API to see which parts of the resource are published. From memory, I would say that the current trend is that the entire resource is published into the message. There is no mechanism for a message consumer to request a specific format from the message producer.
Your point makes sense for a point-to-point communication, but perhaps in that case you should consider creating a new message format specifically for this use case.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------