| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IIB Ignores default values?! |
« View previous topic :: View next topic » |
| Author |
Message
|
| Frik |
 Posted: Wed Aug 26, 2015 6:04 am Post subject: IIB Ignores default values?! |
 |
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
Hello,
Using IIB 9.0.0.3.
We have migarated some of the projects and decided to leave alone the Mxsds (and start using DFDLs in the future).
Now,
There is a mxsd file which have CWF Domain. Every variable in the mxsd have default value.
After mapping node, some of the values are nulls,
and we operate ASBITSTREAM for this message with a specific Message type,set and format.
Unlike WMB 7, IIB ignored the default values.
It seems to happen for fields of the type int/short/long where the default value is 0.
Any suggestions?! |
|
| Back to top |
|
 |
| timber |
| Posted: Wed Aug 26, 2015 3:51 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Are the fields mandatory ( maxOccurs >= 1) ? |
|
| Back to top |
|
|
| Frik |
| Posted: Wed Aug 26, 2015 6:48 pm Post subject: |
|
|
Acolyte
Joined: 25 Nov 2009
Posts: 69
|
|
| Back to top |
|
|
| timber |
| Posted: Thu Aug 27, 2015 1:15 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
Yes, if maxOccurs was 0 they would not appear in the data at all!
I meant to ask about minOccurs!
So..do all of these fields have minOccurs=1? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 27, 2015 2:09 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I just looked at one of my MRM Message Sets that was migrated from 7.0.0.4 to 9.0.0.3
I tested it and have not seen what you are experiencing.
Both MinOccurs and MaxOccurs are 1 but not specifically defined, just defaulted.
All the enumeration settings on the different fields in the Message Set work fine as well.
The migration process was this
1) Import the MessageSet project into the workspace
2) Import the Flow into the Workspace
3) convert the MessageSet project into a Library
4) convert the subflows to use .subflow extensions
5) resolve the other subflow connections using 'locate subflow'
6) convert to Application
7) Create a new Bar file and deploy.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| 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
|
|
|
|
