| Author |
Message
|
| Ashok Kumar |
 Posted: Mon Jul 01, 2013 8:57 am Post subject: Change XML data format to MRM data format using java compute |
 |
|
Acolyte
Joined: 01 Jul 2013
Posts: 53
|
Hi All,
I take xml input data using mq input node .How can we convert the input data to MRM data using java compute node.
Please any one give the answer.
Thank You.
Ashok Kumar |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Jul 01, 2013 8:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Go look at the sample for using JavaCompute node.
You will not get basic step by step assistance here. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jul 01, 2013 9:02 am Post subject: Re: Change XML data format to MRM data format using java com |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| shanson |
| Posted: Wed Jul 03, 2013 6:22 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Message sets are *not* deprecated in v8. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 03, 2013 6:38 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| shanson wrote: |
| Message sets are *not* deprecated in v8. |
They are disabled by default. If you want to use them, you need to enable them.
https://en.wikipedia.org/wiki/Deprecation
| Quote: |
Deprecation is a status applied to a computer software feature, characteristic, or practice indicating it should be avoided, typically because of being superseded. The term is also sometimes used for a feature, design, or practice that is permitted but no longer recommended in other areas, such as hardware design or compliance to building codes.
While a deprecated software feature remains in the software its use may raise warning messages recommending alternative practices; deprecated status may also indicate that feature will be removed in the future. Features are deprecated rather than immediately removed to provide backward compatibility and give programmers time to bring affected code into compliance with the new standard. |
You can say its not "deprecated" but what is your term for the status of the message set feature if not " it should be avoided, typically because of being superseded." by DFDL?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| shanson |
| Posted: Wed Jul 03, 2013 6:54 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Regardless of definitions, the term 'deprecated' has the association in many peoples' minds that the feature will be withdrawn at some point. That is not the case with message sets or MRM. These features will not be withdrawn, hence IBM has deliberately avoided the term 'deprecated'. So please can you avoid using the term also. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 03, 2013 6:58 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| shanson wrote: |
| Regardless of definitions, the term 'deprecated' has the association in many peoples' minds that the feature will be withdrawn at some point. That is not the case with message sets or MRM. These features will not be withdrawn, hence IBM has deliberately avoided the term 'deprecated'. So please can you avoid using the term also. |
I would be glad to avoid using that term. Would you be so kind to suggest one word term that we could use? 'Disabled' and 'deprecated' seem to have the same connotation that we need to avoid.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jul 03, 2013 7:07 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
de-emphasised?
_________________
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 |
|
|
| shanson |
| Posted: Wed Jul 03, 2013 8:07 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
The infocenter uses this phrase in several topics:
| Quote: |
| In WebSphere® Message Broker Version 8.0 and later, message model schema files contained in applications, integration services, and libraries are the preferred way to model messages for most data formats. Message sets are required if you use the MRM or IDOC domains. |
There isn't really a one word term you can use. If you want to model FIX then at the moment you have to use MRM, as IBM's DFDL implementation does not yet have unordered support. So it's not always correct to say that message sets are 'not recommended', for example. Approach it from the other angle - say DFDL / libraries are preferred where possible to MRM / message sets. |
|
| Back to top |
|
|
|
|
