[ https://issues.jboss.org/browse/RTGOV-566?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-566: ---------------------------------- Hi Michael Would have to disagree - the property mechanism within the information processor is intended to extract business relevant information that can be used in policies, not to serialize header values, which are really part of the message. Originally I was looking at using this mechanism, as a potential way to implement your requirement on FSW 6.0 without having to apply a patch. but this didn't work out. So I think the 'serialize' information transformer is the ideal place to handle serialization of not just the mesage payload, but header values aswell. If header values are stored in properties, then the ip.json configuration is more complex as it must list each header value of interest, as well as potentially define its unserialized representation (e.g. dom). It would also not be clear which properties are header values, and which are actually extracted values intended to support policies. I've actually implemented the mechanism described above - it simply requires the 'includeHeaders=true' set on the serialize information transformer, and it will resubmit all string and DOM header properties - the DOM properties are returned in the correct format. Branch: https://github.com/objectiser/rtgov/tree/RTGOV-566 I'll hold off merging until we have had further discussions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)