| Author |
Message
|
| dyson |
 Posted: Tue Jul 31, 2012 3:42 pm Post subject: Debugging the XSL Transform Node |
 |
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
I'm new to using the XSL Transform node and trying to figure out how to step thru the XSLT code referenced in the node. I couldn't find much when I searched for documentation, any help would be great or just a link to a reference would work. I'm using WMB 6.1.0.8
Thanks. |
|
| Back to top |
|
 |
| MBMQDeveloper |
| Posted: Tue Jul 31, 2012 9:30 pm Post subject: |
|
|
Novice
Joined: 02 Jul 2012
Posts: 19
|
Are you trying to debug the XSL being used? If that is the case, this can be done outside MB as well.
As far as I understand, XSL is a third party component being used by MB for transformation and so debugging the same is not possible using toolkit. |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 8:25 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| Correct I'm trying to follow the logic thru this IBM xsl which is huge 8K lines. Unfortunately it looks as if my only option is to debug within the toolkit due to the source of the input so I’m hoping you’re wrong about it not being possible. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 01, 2012 8:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 8:54 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| Well that answers that question and yes I tried the uesr trace not much help. That's cool I'll be here reading thru the 10k lines of code trying to fix IBM's bug ... wish me luck. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 01, 2012 9:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dyson wrote: |
| That's cool I'll be here reading thru the 10k lines of code trying to fix IBM's bug ... wish me luck. |
I'd sooner wish you luck with the PMR. If this is an IBM supplied XSLT then you should be able to get support with it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 9:12 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| Yes I'm familiar with the PMR and if it wasn't POC code then that would be a great suggestion, thanks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 01, 2012 9:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dyson wrote: |
| Yes I'm familiar with the PMR and if it wasn't POC code then that would be a great suggestion, thanks. |
If it's a purchased product it doesn't matter if it's your production system, a POC or something the voices in your head told you to do.
You paid the license. You get the support.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 9:26 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| There are some extenuating circumstances involved so I’m very doubtful but I will try, thanks again. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Aug 01, 2012 11:18 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Correct I'm trying to follow the logic thru this IBM xsl which is huge 8K lines. Unfortunately it looks as if my only option is to debug within the toolkit due to the source of the input so I’m hoping you’re wrong about it not being possible. |
You must really want to do this, because there are much easier and better ways to get to a solution. Have you tried either of the following:
- execute your transform using a free XSLT engine such as Xalan. XSL is a standard, so all implementations *should* behave the same. If you can find another XSL engine that does what you expected then it will be easier to prove to IBM that their XSL engine is at fault. There may even be XSL tools out there which can show you how they arrived at the answer.
- Cut down your input XML and stylesheet to isolate the problem and then post your question on a public forum where real XSL experts are available. ( no disrespect intended to any XSL experts reading this ). |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 12:41 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| It's not the engine I'm worried about. For clarity - I'm taking a binary message with 10 items putting it thru the XSL Transform node and out comes the xml with 7 items. I was hoping to step thru (debug) the xsl used in the XSL Transform node to dertmine the actual cause of the missing items but as I've been told this isn't possible. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 01, 2012 12:43 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I didn't think it was possible to write an XSLT that used a non-XML document as the input.
I guess that's my new thing for the day.
I assume there's some specific, unbendable reason for doing this work using XSLT instead of the much more flexible and user friendly tools that Broker is built and designed to provide? |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 12:58 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| there is a lot of complicated logic that I don't want or have time to recreate in ESQL or java. I think my best bet is to just start reading thru it. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 01, 2012 12:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dyson wrote: |
| It's not the engine I'm worried about. |
I think what my associate is getting at is that another XSL engine like Xalan may have better debugging facilities than the one supplied with WMB.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dyson |
| Posted: Wed Aug 01, 2012 1:04 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2011
Posts: 45
|
| I can be a little slow sometimes ... i'll look into it. |
|
| Back to top |
|
|
|
|
