| Author |
Message
|
| Blackberry |
 Posted: Thu Jun 14, 2007 1:45 am Post subject: setting value into MQRFH2.mcd.Msd |
 |
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
Hi,
My client requirement is to Set a value to MQRFH2.mcd.Msd that is not a valid domain name like 'text_str'. 
I personally don't belief this is possible. Could anybody let me know is there any way to do this in WBI version 6.0.2?
Urgent help required.
Thanks
Blackberry |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jun 14, 2007 1:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You can set it to anything you want. Like the rest of the RFH2.
The wisdom of doing it is rather less clear. Can your client justify this somewhat questionable requirement, or is it just required "because it is"?
Why would you call it something like that? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Blackberry |
| Posted: Thu Jun 14, 2007 2:08 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
Hi Vitor,
I think for my case the second one will be appropiate.
| Quote: |
| Can your client justify this somewhat questionable requirement, or is it just required "because it is"? |
Preveously the message flow was running on 2.1. But now it has been migrated to 6.0 and the problem started just right there. I had checked that the mcd.Msd getting changed with message domain change. That means mcd.Msd get automatically set by the broker with the current domain. Is there any possible way to prevent the change of domain.
Thanks
blackberry |
|
| Back to top |
|
|
| Blackberry |
| Posted: Thu Jun 14, 2007 2:16 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
Vitor,
Could you please tell me how can it be done in WBI 6.0.
| Quote: |
| You can set it to anything you want. Like the rest of the RFH2. |
thanks in advance
Blackberry |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2007 2:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Blackberry wrote: |
Preveously the message flow was running on 2.1. But now it has been migrated to 6.0 and the problem started just right there. I had checked that the mcd.Msd getting changed with message domain change. That means mcd.Msd get automatically set by the broker with the current domain. Is there any possible way to prevent the change of domain.
|
Are you saying the broker is changing the domain to this value? Or that your client has already set the broker to make this change?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2007 2:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Blackberry wrote: |
Could you please tell me how can it be done in WBI 6.0.
|
If I'm reading your previous post correctly, it already has been.
IMHO I wouldn't change it to anything except what it's been originally set to. You could get some very odd results. If it actually worked at all.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Blackberry |
| Posted: Thu Jun 14, 2007 2:34 am Post subject: |
|
|
Apprentice
Joined: 12 Jul 2006
Posts: 28
|
Probably i was not pretty clear in my preveous post.
I have to populate a value in MQRFH2.mcd.Msd like 'text_mrm' in output message. so i am setting
OutputRoot.MQRFH2.mcd.Msd = 'text_mrm';
But this value is being changed to 'xml' (I am using xml domain) in output message. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 14, 2007 2:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Blackberry wrote: |
Probably i was not pretty clear in my preveous post.
I have to populate a value in MQRFH2.mcd.Msd like 'text_mrm' in output message. so i am setting
OutputRoot.MQRFH2.mcd.Msd = 'text_mrm';
But this value is being changed to 'xml' (I am using xml domain) in output message. |
Ah... light dawns! 
You can change the Msd using the kind of code you've posted. I would have expected it to be persisted, but clearly the v6 broker is resetting it on output. Another improved feature of v6.
Tell your client it can't be done because safety code in the broker prevents something this stupid being done. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jun 14, 2007 3:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Msd is just a string value, and it's fine to set it something imaginary, as long as you're willing to live with the fact that it won't be any use further down stream in parsing the message at all.
But in v6, everything that is stored in Properties - of which MessageSet is one - has to be set in Properties. Setting it in the equivalent header field from which it's drawn won't help. Blackberry has proved this for him or herself already.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
