| Author |
Message
|
| Vgowda |
 Posted: Tue Feb 14, 2012 1:47 am Post subject: Accessing Current TimeStamp from XSLT in WMB |
 |
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
Hi,
Is there a way to access CURRENT_TIMESTAMP in XSL Transform node? I am creating a message in XSL, in that i need to populate CURRENT_TIMESTAMP for one of the field.
Any thoughts on this would be helpful.
_________________
Regards
Vinay |
|
| Back to top |
|
 |
| Vgowda |
| Posted: Tue Feb 14, 2012 2:00 am Post subject: |
|
|
Acolyte
Joined: 11 Dec 2007
Posts: 61
Location: Bengaluru
|
|
| Back to top |
|
|
| mqsiuser |
| Posted: Tue Feb 14, 2012 2:01 am Post subject: Re: Accessing Current TimeStamp from XSLT in WMB |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| Vgowda wrote: |
Hi,
Is there a way to access CURRENT_TIMESTAMP in XSL Transform node? I am creating a message in XSL, in that i need to populate CURRENT_TIMESTAMP for one of the field.
Any thoughts on this would be helpful. |
No and Yes.
I remember that I used to put an ESQL node behind the XSLT... but one day a collegue showed me something, where you can use XSLT 2.0 functions or some xslt utilites that you need to bring in or something, where this also works directly in XSLT 
Ah, I remember... it works only in Broker (and not in XML-Spy  . So not perfectly easy to develop.
I don't remember exactly - have fun
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Tue Feb 14, 2012 2:04 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
I think you are on a good track.
Though the Broker-Version I used didn't support XSLT 2.0, so you need to use the "extension package" (which you install on Broker runtime, and then... this wouldn't work in XML-Spy).
Andy Pieper writes "as I understand it, XSLT 2.0 support may arrive sometime after WMB v8 GAs in December – I’m not sure that you can make it work in v7, certainly not using the XMLTransform node."
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| goffinf |
| Posted: Thu Feb 16, 2012 11:54 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Yep you have 3 options :-
1. Use XSLT2
2. Use the EXSLT library
3. Pass it into your XSLT as a parameter.
Obvious (1) is not possible at present (it's one of the reasons we use a custom node for XSLT).
Fraser. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Feb 16, 2012 5:08 pm Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| goffinf wrote: |
Yep you have 3 options :-
1. Use XSLT2
2. Use the EXSLT library
3. Pass it into your XSLT as a parameter.
Obvious (1) is not possible at present (it's one of the reasons we use a custom node for XSLT).
Fraser. |
Added to "3.": Or fix after the XSLT-transform (though passing in is probably better)
Option 4. Use ESQL (only) instead of XSLT.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
|
|
