| Author |
Message
|
| whydieanut |
 Posted: Thu Oct 15, 2015 7:48 pm Post subject: Code Coverage for XSLT Node |
 |
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Hi everyone,
We are trying to get Code Coverage reports for our flows.
We are currently using IAM2 for ESQL and are looking for something similar for XSLT nodes.
All I could find for XSLT are tools that work outside of WMB; and I am not sure if they can be integrated into WMB.
Is there any way to enable detailed tracing for XSLT? If so, I don't mind rolling my own solution, something similar to what IAM2 does.
The infocenter has this:
| Quote: |
Trace setting:
This property is deprecated. Start user trace instead. The user trace contains the same XSL trace information. If you set this property, it does not affect user trace.
In previous versions of WebSphere Message Broker, this property controls whether tracing is on or off. If tracing is on, low level tracing is recorded in a file. |
But I couldn't find any detailed XSLT related entries in the User trace. I however saw some entries in XMLTTrace.log but nothing that could be used for Code Coverage. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Oct 16, 2015 12:36 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
XSLT is a total black hole when it comes to usertrace.
Debugging XSLT is hit and miss at the best of times but ... in fact I'd rather code in Java than use XSLT and I'm up there with vitor in my dislike of Java.
_________________
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 |
|
|
| whydieanut |
| Posted: Fri Oct 16, 2015 1:49 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Is it entirely futile to try and find a solution or is there some hope of mashing up some existing XSLT tool with WMB?
The thing is, we have flows using XSLT and can't wish them away (or move them to ESQL).
Not related, but with respect to maintainability and performance, does the mapping node make more sense than XSLT? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 16, 2015 4:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| whydieanut wrote: |
Is it entirely futile to try and find a solution or is there some hope of mashing up some existing XSLT tool with WMB?
The thing is, we have flows using XSLT and can't wish them away (or move them to ESQL).
Not related, but with respect to maintainability and performance, does the mapping node make more sense than XSLT? |
Create your own test bed and compare. As in all these cases there is no straight answer. (YMMV). 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 16, 2015 4:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| whydieanut wrote: |
| some hope of mashing up some existing XSLT tool with WMB? |
There's always hope. There's hope that some 18 year old beauty contest winner will jump into my lap and declare her unending love for me. Realistically there's more chance I'll be elected Emperor Of The World, or that you'll mash something together that's suitable or maintainable.
| whydieanut wrote: |
| The thing is, we have flows using XSLT and can't wish them away (or move them to ESQL). |
This migration exercise would be trivial compared to producing a code coverage tool for XSLT, and much more productive in the long run.
| whydieanut wrote: |
| Not related, but with respect to maintainability and performance, does the mapping node make more sense than XSLT? |
Much, much more sense. In any version of WMB still supported.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| timber |
| Posted: Fri Oct 16, 2015 5:28 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| with respect to maintainability and performance, does the mapping node make more sense than XSLT? |
Taken as a stand-alone question, the answer is 'yes, usually'.
However, if you were thinking of *migrating* from XSLT then you would need to consider all of the usual factors before deciding on which transformation language to migrate to. The answer still might be the Mapping node, but it might be ESQL. Or even ( horrors!) well-written Java. |
|
| Back to top |
|
|
| whydieanut |
| Posted: Sun Oct 25, 2015 7:50 pm Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Again on an slightly unrelated note,
IAM2 doesn't give a report on the list of nodes traversed.
I am planning on extending the script to do that as well.
I am almost half way through, but is there something like this already available? |
|
| Back to top |
|
|
|
|
