Message compare excluded paths

centeractive people
Posts: 44
Joined: 11 Sep 2012, 20:27

Message compare excluded paths

Postby waclaw » 22 Nov 2012, 21:23


I've got a following question: why in message comparison components for some comparison modes the excluded paths edit box is enabled, and for some it is disabled? Disabling doesn't even protect it from modifications, because it is possible to change its content with other comparison mode selected, and then select comparison mode, which has the field disabled. Field's content is preserved.

centeractive people
Posts: 68
Joined: 06 Jun 2012, 16:45

Re: Message compare excluded paths

Postby urs.minder » 23 Nov 2012, 07:44

"Excluded Paths" are XPath expressions that identify XML elements to be excluded entirely from the comparison process. Comparison is done on the XML representation of individual messages. Therefore for being able to define valid XPath expressions, one has to know about the XML representation of messages. Excluded paths are considered only for the following comparison modes:
  • compare all for equality
  • compare all for equality (include nested XML)
  • compare equality not structure
All these comparison modes basically compare the whole structure of two messages except the parts defined by excluded paths. This is typically used to exclude message control elements that are of no evident business relevance.

When you select a comparison mode where excluded paths are not considered, the “Excluded Paths” field is disabled but its content remains unchanged. That way it becomes again available in you switch back to one of the above listed comparison modes.

Return to “General Opensphere Topics”

Who is online

Users browsing this forum: No registered users and 1 guest