Author |
Message
|
sai kumar adduri |
Posted: Mon Jul 01, 2013 8:47 am Post subject: transformation using mapping node in wmb 8 |
|
|
Acolyte
Joined: 04 Apr 2013 Posts: 73
|
I want to perform xml to csv transformation using mapping node.
I have created message sets for both xml and csv .
the error which I am getting is Could not resolve schema /MSG_CSV/TXT.mxsd. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Jul 01, 2013 8:50 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
goffinf |
Posted: Mon Jul 01, 2013 1:36 pm Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005 Posts: 401
|
lancelotlinc wrote: |
In WMB 8, Message Sets are deprecated ... |
It seems to me that IBM are very keen to make it clear that this is NOT the case. They also typically state that DFDL would be the preferred option for new flows, but message sets remain a supported part of the product. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jul 01, 2013 10:44 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
goffinf wrote: |
It seems to me that IBM are very keen to make it clear that this is NOT the case. |
Exactly my thoughts. Even more, I setup a VM with Broker 9 yesterday and deployed some message flows and message sets from V7.0.0.4 right into it and everything worked. Ok, so not an exhaustive test yet by they ain't going away. _________________ 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 |
|
 |
sai kumar adduri |
Posted: Tue Jul 02, 2013 12:20 am Post subject: |
|
|
Acolyte
Joined: 04 Apr 2013 Posts: 73
|
Done this using DFDL , but getting an error while working with message sets , is there any reason for this and any way to use message sets |
|
Back to top |
|
 |
kimbert |
Posted: Tue Jul 02, 2013 12:54 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
OK, time to state some facts:
- v8 will run any v7 message flow without modification. If it doesn't, it's a defect.
- The MRM domain and message sets remain a fully-supported part of the product. They are not deprecated and will be supported for many releases to come.
- IBM recommends that new message flows should use DFDL for parsing text and binary data - DFDL is better than MRM at most things.
Or, to put it more simply, DFDL is now the strategic technology and the MRM domain is de-emphasised in favour of DFDL. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 02, 2013 3:29 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sai kumar adduri wrote: |
Done this using DFDL , but getting an error while working with message sets , is there any reason for this and any way to use message sets |
If you've got it working in DFDL why would you want to use a message set? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
sai kumar adduri |
Posted: Tue Jul 02, 2013 5:35 am Post subject: |
|
|
Acolyte
Joined: 04 Apr 2013 Posts: 73
|
since it was a simple message i have created DFDL , what if the message is a bit complex .
How do we add a sub complex type when we use DFDL |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jul 02, 2013 6:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
A DFDL is just an XML schema with some annotations.
You add a "sub complex type", whatever that is, by using the DFDL model editor to add a child element or add a complex type and then create an element of that type.
The exact same way you would do it in MRM. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Jul 03, 2013 2:14 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sai kumar adduri wrote: |
since it was a simple message i have created DFDL , what if the message is a bit complex . |
If the message is a bit complex, a lot complex or enough to make your brain leak out of your ears you still use DFDL.
I would put it to you that if the message is "too complex" for DFDL you've got no chance building a message set that will cope. There are DFDL schemas on GitHub for industry formats MRM can't manage (due to limited MRM bit level support) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|