MQSeries.net :: View topic

matthewmatcham · Posted: Mon Aug 23, 2010 4:54 am Post subject:

Broker version 6.1.0.2 on Windows

I have a flow with a SOAPInput node and have set the Parse timing to 'Immediate'. I am trying to handle and log errors from this node and create a SOAP Fault with some simple ESQL and a SOAPReply node. I'm sending messages from soapUI with invalid content that will fail parsing.

When I invoke the flow from soapUI the CCSID of the request is 1208, and the reply obviously needs to match this. However the value in Root.Properties.CodedCharSetId is 1252 immediately after the SOAPInput node. Any attempt to create a SOAP Fault manually in ESQL fails in soapUI due to a CCSID mismatch, and the value 1208 just isn't available to me anywhere in the flow.

If I wire the SOAPInput node directly into a SOAPReply node, and let the Broker create a SOAP Fault, it uses 1208 as the CCSID and everything is good. So it knows it, but doesn't let me see it.

Also, if I change the Parse timing to 'On Demand', the value of Root.Properties.CodedCharSetId becomes 1208 (i.e. the correct value) immediately after the SOAPInput node, and I can now access Root to generate, handle and log an exception and manually create a SOAP Fault to reply with.

I would rather have the SOAPInput node validate the input message immediately, particularly as I'm not actually accessing the message straight away in my flow. However, given my requirements to handle and log the error, it seems this feature (??) is going to force me to use On Demand parsing and place a dummy compute node at the start of my flow to force validation.

Any thoughts? Thanks