| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Validating HTTP Response Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| Svp |
 Posted: Thu Apr 29, 2010 10:00 am Post subject: Validating HTTP Response Message |
 |
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
In a HTTP Request node I set the
Response Message Parsing - Domain to XMLNSC and Message Set to X.
Validation - Content and Value. Failure Action - ExceptionList
Parser Options - On Demand or Immediate
When I get the bad Http response message it never get validated. I am receiving the invalid message which I am not supposed to get. Is there anything else I have to configure? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Apr 29, 2010 1:15 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hard to comment without more details.
- In what way is the message 'bad'?
- Have you experimented with the default option 'Exception' instead of 'ExceptionList'? |
|
| Back to top |
|
|
| Svp |
| Posted: Thu Apr 29, 2010 1:49 pm Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010
Posts: 40
|
| If the response message is a BLOB or invalid xml message, Http request node is not validating against the given Message set. 'Exception' didnt work either. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Apr 29, 2010 2:17 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
All messages are BLOBs when they arrive at an input node. I presume you mean that it's a BLOB that does not contain a well-formed XML character stream.
If Parse Timing is 'On Demand' and the message flow does not need to access any of the message body, then the parser will never be invoked and an invalid message may well get passed on. If you want to ensure that validation takes place, set Parse Timing to 'Immediate'.
If you still think there's a problem with the product, you might like to prove it by supplying all of the details, including
- the input XML
- the schema
- a user trace which shows the output from a Trace node positioned immediately after the Input node.
If you don't want to post details of your business data, any invalid combination of schema/XML will do. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
