| Author |
Message
|
| MQEnthu |
 Posted: Mon Oct 06, 2008 8:57 pm Post subject: Problem with XMLNSC domain in V6.1 during migration |
 |
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
Hi All,
We are facing some problem when a message flow (XMLNSC domain is specified in the input node and immediate volition option is set) developed in V6.0 is deployed to V6.1 run time. The error number is 5027 - validation is enabled but no message set is specified. When I checked the V6.1 documentation, I got to know that in WMB V6.1 message set is mandatory when the validation is enabled for XMLNSC domain. Since message set was not needed for XMLNSC domain in version 6 (in fact the message set field used become non editable when the domain was selected as XMLNSC), there was no message set specified. When these kind flows are deployed to V6.1 broker run time, we are getting the error 5027 - validation is enabled but no message set is specified.
Could any one please let me know how to resolve this problem?
(Work around for this would be changing the domain to XMLNS but I am looking for a solution where I do not have to change message domain). Kindly let us know your views. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Oct 07, 2008 3:07 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| XMLNSC did not support validation in v6.0. The simplest fix is to set Validation to 'None' - it will not change anything because you were not getting any schema validation in v6.0 anyway. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue Oct 07, 2008 3:33 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
Hi Kimbert,
Thank you for the answer.
If I understand correctly, we just have to create the message set and not the message definition. So with out defining structure of the message (with out the schema reference), how will it validate against a schema. Is there any option on V6.1 to specify the schema while creating the message set? |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Oct 07, 2008 4:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| If I understand correctly, we just have to create the message set and not the message definition. |
No - that's not right. The validation is *schema* validation. The schemas are held in the message definition files within the message set. So if you don't have any message definition files, you will get validation error as soon as you attempt to validate a message.
| Quote: |
| Is there any option on V6.1 to specify the schema while creating the message set? |
Of course. It's all described in the docs. Just right-click the message set and select 'New/Message Definition File From/XML Schema File'. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue Oct 07, 2008 4:57 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
Hi Kimbert,
Yes, there is option to create message definition using schema or copy book. But sorry for not being clear in my earlier post. My question is, there is option to specify message name or message format when the domain is selected as XMLNSC in V6.1. There is only option to mention message set id. (I mean message name and message format fields are enabled when the domain is selected as MRM along with the message set but only the message set field is enabled when the domain is set to XMLNSC ) |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Oct 07, 2008 5:34 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
That's correct. XMLNSC does not use MessageType or messageFormat. Those are used by MRM only.
By the way, XMLNSC does not use the information in messageSet.mset. It only uses the schemas which are deployed in the xsdzip. So don't expect the namespace mappings in the message set to be used by XMLNSC. Apologies if you already knew that. |
|
| Back to top |
|
|
|
|
