| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cannot Change the Root.Properties.ReplyProtocol field |
« View previous topic :: View next topic » |
| Author |
Message
|
| ccrandall |
 Posted: Fri Jul 02, 2010 8:28 am Post subject: Cannot Change the Root.Properties.ReplyProtocol field |
 |
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
Hello. I'm making a change to my Message Broker framework to handle SOAP messages. Under MB 6.1, we used SOAPInput nodes with a corresponding Message Set to handle SOAP messaging. However, we quickly found that this approach wasn't very scalable. Also, we are using DataPower for security and validation, so there didn't seem to be a lot of advantages to using SOAP Input nodes in our case.
So, I'm recoding our framework now under MB 7.0.0.0 and we are using a HTTP Input node to receive the SOAP message. Then I have a Compute node that takes the InputRoot and creates an OutputRoot under the SOAP domain. I'm trying to model the resulting message to look like it did previous with the SOAP Input node under MB 6.1.
The problem I'm running into now is that I cannot seem to set the OutputRoot.Properties.ReplyProtocol to 'SOAP-AXIS2'. It's insisting on using the value on the InputRoot.Properties.ReplyProtocol of 'SOAP_HTTP'.
I am trying to change the ReplyProtocol because this framework supports regular HTTP messaging and SOAP and ReplyProtocol has been used to differentiate between the two types. I know I could probably key off the URL, but 1.) I don't really want to make changes if I can avoid it and 2.) I want to know why I'm not able to alter this field for my own knowledge.
I apologize if this has been dealt with before in a previous post, but I wasn't able to find it when I attempted to search for something similar. I did see a thread where someone wanted to set the ReplyProtocol to 'MQ', but I did not see a resolution.
Any help with this would be GREATLY appreciated!
Thank you!
Curt |
|
| Back to top |
|
 |
| gs |
| Posted: Fri Jul 09, 2010 7:36 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
|
| Back to top |
|
|
| ccrandall |
| Posted: Fri Jul 09, 2010 1:16 pm Post subject: |
|
|
Acolyte
Joined: 23 Oct 2008
Posts: 52
|
Thank you for the link. I did catch that one earlier and it is similar, but still doesn't really explain why you cannot change the ReplyProtocol.
For me, this is strictly a convenience because we handle both HTTP and SOAP over HTTP traffic. Keying off the ReplyProtocol made it easy to distinguish the two because the HTTP Input set it as 'SOAP_HTTP' and the SOAP Input sets it as 'SOAP-AXIS2'.
However, now I've switched from the SOAP Input node to the HTTP Input node followed by a compute node, the ReplyProtocol is the same regardless of whether it's plain HTTP or SOAP over HTTP. But, I guess I can check for the presence of Root.SOAP.Context.* and use that to differentiate. Not a big deal, but just forces me to do a little bit of recoding. |
|
| 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
|
|
|
|
