| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message model or message set? |
« View previous topic :: View next topic » |
| Author |
Message
|
| grasher134 |
 Posted: Fri Feb 19, 2016 5:57 am Post subject: Message model or message set? |
 |
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
Hi,
I'm a bit confused. When you are trying to add a message model to validate input message or to simply help you to write esql code(it becomes difficult with huge xmls) it asks you to provide message set (though the field name says - message model).
Message set's description in "Help" says that
"Tip: A message set is the original container for message models used by IBM® Integration Bus. In WebSphere® Message Broker Version 8.0 and later, message model schema files contained in applications and libraries are the preferred way to model messages for most data formats. Message sets continue to be supported, and are required if you use the MRM or IDOC domains. "
So in other words, guys, use it only for MRM and IDOC if you have to. If don't - stop as it is kinda deprecated feature.
So is this a bug, that message model field in the input node requires message set, or it is the way it should be? Or was it changed in iib 10?
I haven't used it so much yet, only if I had to create my own soap nodes. I'm going to move to iib 10 in a few months (4-6), so my question is whether I should use them(I have some projects, where context help could save me hours of debugging, and in some, message validation would be a great thing) or wait some more time and use something else?
EDIT: Forgot to mention, IIB v 9.0.0.5 + toolkit v9.0.0.4 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 19, 2016 6:08 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
For the purpose you mentioned message sets and message models should be interchangeable. However keep in mind that in across your message models you should not have the same xsd more than once per application space ... , so be careful if you have more than one library in an application; which may be a little bit of a challenge if you are used to message sets where it is once per message set... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| timber |
| Posted: Fri Feb 19, 2016 6:20 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| However keep in mind that in across your message models you should not have the same xsd more than once per application space ... , so be careful if you have more than one library in an application; which may be a little bit of a challenge if you are used to message sets where it is once per message set... |
Sound advice for users of WMBv8 and IIBv9.
From IIBv10 onwards, a shared library is a self-contained model ( just like a message set ). So the same xsd ( or more generally, the same qualifiied XML name ) can be used in two or more shared libraries within the same application. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 19, 2016 7:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| timber wrote: |
| Quote: |
| However keep in mind that in across your message models you should not have the same xsd more than once per application space ... , so be careful if you have more than one library in an application; which may be a little bit of a challenge if you are used to message sets where it is once per message set... |
Sound advice for users of WMBv8 and IIBv9.
From IIBv10 onwards, a shared library is a self-contained model ( just like a message set ). So the same xsd ( or more generally, the same qualifiied XML name ) can be used in two or more shared libraries within the same application. |
As you did not mention -non shared libraries-, I guess that restriction is still valid for those..., or would that mean that if you have a mix of shared and non shared libraries you cannot have an xsd in a non shared library if it is already present in a shared one within the same application?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| timber |
| Posted: Fri Feb 19, 2016 8:14 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| would that mean that if you have a mix of shared and non shared libraries you cannot have an xsd in a non shared library if it is already present in a shared one within the same application? |
It's a good question, and I purposely dodged it when replying earlier. I'm honestly not sure what the anwer is. Technically, I think it could be made to work, but the toolkit's validation engine might prohibit it anyway. |
|
| 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
|
|
|
|
