| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Mapping Node or Transformation Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| team |
 Posted: Tue Jan 02, 2007 2:51 am Post subject: Mapping Node or Transformation Node |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 108
|
Hi,
I need to convert an incoming XML to another XML / Tag Delimited format. I have incoming xsds.
I wanted to know, which would be a better node to use : Mapping Node or XML-Transformation Node.
Please could you advise.
Thanks
Team |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jan 02, 2007 2:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Which one is better for you?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| team |
| Posted: Tue Jan 02, 2007 3:35 am Post subject: Transforamtion Node / Mapping Node |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 108
|
I am new to this transformation and would like to know the adv/disadv with regard to:
1) Ease of use
2) Capability
3) Performance
Thanks
Team |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 02, 2007 4:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Which one is easier for you to use?
They are both equally capable.
You would have to measure the performance yourself, as it can vary quite a lot.
Using the XML Transformation node, in my opinion, though, is not using Broker at it's best. It's essentially ignorning all of the capabilities of Broker in order to use XSLT instead of ESQL or Java. I personally would not use XMLTransformation node unless there was an existing XSLT transformation that needed to be re-used.
There isn't a clear answer to your question. Try stuff. Learn stuff.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Jan 07, 2007 8:33 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
To emphasize on Jeff's statement.
I have seen a mapping in which every element in the output message was repeatable (messages had to be imported from a schema), in V5 that means a sub-mapping for every element. XSLT was not only easier but also faster, even in V5.
Also, XSLT has more dynamics, you can compute what xslt to use (from a database?).
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| 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
|
|
|
|
