| Author |
Message
|
| vandi |
 Posted: Sat Jan 31, 2009 6:18 pm Post subject: XSLTs Pros and cons over ESQL in a msgflow |
 |
|
Acolyte
Joined: 13 Dec 2008
Posts: 67
|
Hi All,
I have a doubt regarding XSLT's. Can anyone of you pls let me know the pros and cons of using XSLT's in Transformation of Messages from one form of XML to other form over ESQL coding and Mapping techiniques in a message flow.
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Feb 01, 2009 5:12 am Post subject: Re: XSLTs Pros and cons over ESQL in a msgflow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vandi wrote: |
| I have a doubt regarding XSLT's. |
This doubt being.....?
| vandi wrote: |
Can anyone of you pls let me know the pros and cons of using XSLT's in Transformation of Messages from one form of XML to other form over ESQL coding and Mapping techiniques in a message flow.
|
Well if your existing (pre-WMB) process uses XSLT it saves you rewriting everything. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vandi |
| Posted: Sun Feb 01, 2009 9:27 am Post subject: |
|
|
Acolyte
Joined: 13 Dec 2008
Posts: 67
|
Hi,
Thanks for your reply Vitor. I know that using XSlt's avoids rewriting, but we are rightnow in design stage and wanted to know performance wise XSLT's are better or coding in ESQL or mapping.
Thanks
Vandi |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Feb 01, 2009 10:51 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi vandi,
I suppose the difference would be negligible, but I'm not entirely sure.
I would base my choice on the fact that esql helps me code additional business logic, which I doubt xslt can. xslt would be closer to the functionality of a mapping node, but that too provides a lot of function calls, java calls etc, so xslt would be found lacking.
Regards. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Feb 01, 2009 11:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If your performance goals are to transform one message every hour, then you will not notice a performance difference between XSLT, ESQL, Mapping, Java, PHP, or a C custom node. These are all of the options you have for writing logic in Broker right now.
If your performance goals are to transform one message every nanosecond, then you will have to spend quite a lot of time measuring everything and testing everything and tweaking everything, including testing each of the various different mechanisms for performing the transformation.
If your performance goals are somewhere in between these two points, then many other decisions you make will have as much impact on performance as the choice of what to execute your logic in.
Generally, XSLT is only chosen for use in Broker by most people when it is either being used to reuse existing logic, or when it is the only thing they have any development skill in at all. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Feb 01, 2009 11:19 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The real answer (IMHO) is
IT DEPENDS upon many factors.
If your XSLT is simple and you don't have to transform many message per hour OR performance is no problem then, an XSLT may very well be the best solution to use.
If however the XSLT is complex then Broker with XSLT may not be the best solution.
One one system I worked on, we modified a flow to remove the XSLT and coded the transofrmation in ESQL. We got 4x the throughput.
The downside was that changes were going to be much harder to implement but that was a risk that the customer was willing to take.
_________________
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 |
|
|
| kirank |
| Posted: Mon Feb 02, 2009 2:46 pm Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
One advantage of XSLT is is that it is an open standard and not proprietary like ESQL. However whenever I have used XSLT with broker, I have observed that XSLT has some limitations on transformations. For simple XML to XML transformations it works well. However if your transformations are heavy duty including non-XML data then you are better of using ESQL.
Regards
Kiran |
|
| Back to top |
|
|
|
|
