| Author |
Message
|
| Maria_123 |
 Posted: Thu Jan 11, 2007 9:37 pm Post subject: Mapping |
 |
|
Novice
Joined: 05 Oct 2006
Posts: 22
|
I have read in a post before that the XML transformation node does not use the broker to its best.
Could you substantiate please. Is it not that XSLTs are very easy to create and light on the broker?
Thanks,
Maria |
|
| Back to top |
|
 |
| mapa |
| Posted: Fri Jan 12, 2007 12:32 am Post subject: Prev post |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 12, 2007 2:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The XMLTransformation node only works on data in the BLOB domain.
It also only works on... XML data!
Broker provides good tools for modeling all kinds of data - so that it can parse the physical message and turn it into a logical message tree. Then your code can be written to deal with the logical message tree and never have to know that a particular piece of data is XML or a C record or whatever!
If all you are doing is XSLT transformations, then you are paying a good deal of money for Message Broker for powerful features that you are not using. Use WebSphere Enterprise Service Bus or some other XSLT transformation engine instead.
This is just my opinion.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Maria_123 |
| Posted: Fri Jan 12, 2007 4:43 am Post subject: Mapping |
|
|
Novice
Joined: 05 Oct 2006
Posts: 22
|
Thanks for ur reply....
Currently the entire appllication that we are using is being developed in WBIMB......and hence we dont want to shift to use a different XSLT engine...However considering ease of creation and maintenance as well as future use of the technology I feel that XSLTs would be easy to develop.
Thanks,
Maria |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 12, 2007 6:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
XSLTs can only transform data that starts out as XML data.
The Message Broker Toolkit on it's own does not include any assistants for developing XSLT transformations - the GUI mapper can't export to XSLT for example.
There may be functionality that comes with the Toolkit, because the Toolkit is built on top of Rational Application Developer.
If you've paid for broker, it is best to get the most value you can out of it - it's not inexpensive.
It is a false economy to ignore 90% of the capabilities of a product to potentially save money in the future when you might move to a different platform.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
