MQSeries.net :: View topic - Remove logical fields when physically rendered

gpkssts · Posted: Tue Nov 22, 2005 5:25 am Post subject:

I've got a flow that handles many different message types, parsing use the ESQL CREATE .. PARSE, basing message type on a field in the RFH2 header. That all works fine.

But as an enhancement what I would like to do now is be able to specify a different message set in the properties folder to be able to cause some of the logical fields to be removed (the message type would still have the same name). This would allow me to use the flow to deliver the same logical message to different applications but with some applications not receiving some of the information.

All of the messages are defined in the MRM. Its like I'd like to be able to specify the complex types as having Compositon=sequence and Validation=Closed++ with this option ensuring that the fields defined are present but any extra are dropped.

I'm thinking it can't be done at the render stage from what I've tried/read but wondered if anyone else had cracked it. It seems a basic thing to be able to do but I know that this doesn't always imply that it is. Because of the message naming standard I could do it in ESQL or XSLT for my current need. But walking down the structures in ESQL and testing names though easy will probably have some performance impact. I haven't done enough with XSLT to know whether it would have the same performance impact but I'd expect so. (Not being able to manage the XSLT deployment in the bar on the v5 we have here also puts me off that)