| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Does WSMB 8.0.0.1 really support XSLT 2.0 as stated in docs? |
« View previous topic :: View next topic » |
| Author |
Message
|
| t603 |
 Posted: Wed Nov 14, 2012 6:06 am Post subject: Does WSMB 8.0.0.1 really support XSLT 2.0 as stated in docs? |
 |
|
Voyager
Joined: 16 Oct 2012
Posts: 88
Location: Prague, the Czech Republic, Europe
|
Hello,
I have a problem. I was not able to write XSL-T 2.0 transformation in WSMB 8.0. There is list of supported standards in WSMB 8.0.0.1 in its documentation on the page http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/ah36080_.htm, where is also written:
| Code: |
XPath - 1.0
XSL - 1.0, 2.0 for use with the XSLTransform node
XSLT - 1.0, 2.0 |
Although I do not know difference between XSL and XSLT (should not be there rather XSL-T in accordance with with naming convention and existence of XSL-FO?) and I am not sure about existence XSL-T 2.0 without XPath 2.0, I would like to be sure, that WSMB 8.0.0.1 :
1) really supports XSL-T 2.0 within XSLT node (NOT my self external calling of any Java code ~ Saxon) ~ and thus I am dumb not to be able to use it just switching from XSL-T version="1.0" to version="2.0",
2) which part of XSL-T 2.0 supports (any compatibility matrix with W3C reccomendation would be great),
3) how supports XSL-T 2.0 without XPath 2.0 (because, AFAIK XPath and XSL-T share functions)
4) which XSL-T engine is used (I guess, it could be the engine inside IBM - WebSphere Application Server Feature Pack for XML or is it Saxon and if Saxon, which edition HE, PE, EE and version?)
5) are there any samples of using XSL-T 2.0 using XSLT transformation node
6) is it possible to read (and write in the same level as in ESQL) not only Message, but also Environment, LocalEnvironment and Exception within XSLT transformation node.
7) are there any performance white papers for XSL-T 2.0
8) is it necessary to do any configuration of WSMB to enable XSL-T 2.0 in XSLT node.
After all any documentation about using XSL-T 2.0 in WSMB 8.0.x would be great. Maybe there is any documentation, but I am not enough skilled to find it using Google (I used "websphere message broker 8.0 xslt 2.0") just now 2012-11-14.
Thank You for Your answer in advance. Stepan |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Wed Nov 14, 2012 6:26 am Post subject: Re: Does WSMB 8.0.0.1 really support XSLT 2.0 as stated in d |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| t603 wrote: |
| 7) are there any performance white papers for XSL-T 2.0 |
from Performance, efficiency, and cost issues:
| Quote: |
| Performance, efficiency, and cost issues include asset reuse, speed and cost of development, and runtime performance. The ability to reuse an asset such as an extensible stylesheet can reduce development costs, but may impact run-time performance, depending on the type and complexity of processing involved, since performance of an extensible Stylesheet is generally slower than a hand-coded implementation in ESQL or Java. If message throughput is a primary consideration, ESQL or Java is probably a better choice for your processing logic. |
This holds also true for any subsequent version of xslt (because it is an inherent problem of xslt) and explains the lack of information (interest) that you are experiencing.
The cited text is also in conflict with what you write:
| t603 wrote: |
| I was not able to write XSL-T [2.0] transformation in WSMB 8.0. |
Besides performance XSLT also has viewer capabilities than e.g. ESQL (e.g. can't access a database).
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| t603 |
| Posted: Wed Nov 14, 2012 7:01 am Post subject: |
|
|
Voyager
Joined: 16 Oct 2012
Posts: 88
Location: Prague, the Czech Republic, Europe
|
| Quote: |
| from Performance, efficiency, and cost issues |
I studied guess well several times Performance White papers from IBM regarding XSL-T performace, but I asked form performance issues to the XSL-T 2.0 and XSL-T processor. Because there are significant performance differences (like indexing, internal translating of transformation to Java bytecode and other performance improvements) even in different editions of Saxon (HE vs EE) for example, although I guess, that Saxon is not (unfortunately from my point of view) used in XSLT node in WSMB.
Although I came from XSL-T 2.x, up-to-date SQL, in-memory databases and similar technologies few months ago, I certainly do not discuss the (dis-)advantages of XSL-T 2.0 and ESQL here, although my preferences could be estimated straightforward ;-) I am just asking humbly broker gurus for an advice.
I just want to know, if and how to use XSL-T 2.0 (and with Environments, LocalEnvironments, Properties, headers etc.) and I have not found about XSL-T 2.0 nothing but 2 lines of standards in documentation (infocenter) of WSMB 8.0.0.1. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Wed Nov 14, 2012 7:29 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| t603 wrote: |
| I studied guess well several times Performance White papers from IBM regarding XSL-T performace |
Do they say the same. Or are they diplomatic ?
| Quote: |
| but I asked form performance issues to the XSL-T 2.0 and XSL-T processor. |
Why should they change away from xalan?... when I used it (the XSLTransform-Node) there were logs that made it clear which engine they use.
They use a publicly available engine which is just integrated.
| Quote: |
| I am just asking humbly broker gurus for an advice. |
I guess they don't use xslt, which makes answering your question hard for them.
| Quote: |
| and with Environments, LocalEnvironments, Properties, headers etc. |
You can't access these from xslt. xslt is for the payload/body only. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 14, 2012 8:04 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
6) is it possible to read (and write in the same level as in ESQL) not only Message, but also Environment, LocalEnvironment and Exception within XSLT transformation node.
|
No, not as far as I know.
For the other questions, I think the fastest way to answer them would be to try some XSL 2.0 functions in the XSL Transform node and see what happens. I agree that it should be documented, but I'm just being pragmatic. |
|
| Back to top |
|
|
| t603 |
| Posted: Wed Nov 14, 2012 8:14 am Post subject: |
|
|
Voyager
Joined: 16 Oct 2012
Posts: 88
Location: Prague, the Czech Republic, Europe
|
| Quote: |
| Do they say the same. Or are they diplomatic? |
As I understood for WSMB 7.x: more complicated transformation and (or) more larger XML, less performance difference. So for small and simple transformation ESQL is more efficient. In WSMB 7.0 there should be significant (big) XSLT performance improvement.
| Quote: |
| Why should they change away from xalan? |
1) Xalan (both C and Java version) does not and will not (at least for the foreseeable future) support XSL-T 2.0 and XPath 2.0 (at least according to the last posts to developer and user mailing list of Xalan).
2) AFAIK, Xalan lost developer effort support for long time till few months ago. Almost Xalan was moved among Apache attick (sleeping) projects about year ago. AFAIK, former Xalan developers were employees of IBM and since IBM has its own XSL-T 2.0 engine...
3) IBM released its own XSL-T 2.0 engine supporting XPath 2.0, XSLT 2.0, and XQuery 1.0.
| Quote: |
| You can't access these from xslt. xslt is for the payload/body only. |
I could imagine, it could not be very hard to expose metadata of message to the XSL-T engine interface for reading and even writing, so that is why I asked, if it is or it is not exposed.
| Quote: |
| For the other questions, I think the fastest way to answer them would be to try some XSL 2.0 functions in the XSL Transform node and see what happens. |
Of course I did it - write very simple XSL-T transformation, just use new 2.0 function and change version number in XSL-T code header from 1.0 to 2.0 and I received an error - something like "...not supported... or unknown". So that is why I asked.
Anyway, I did not found any info about XSL-T 2.0 but those two lines in standard.
|
|
| Back to top |
|
|
| mqsiuser |
| Posted: Wed Nov 14, 2012 8:27 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| t603 wrote: |
| As I understood for WSMB 7.x: more complicated transformation and (or) more larger XML, less performance difference. So for small and simple transformation ESQL is more efficient. In WSMB 7.0 there should be significant (big) XSLT performance improvement. |
When I last read them (the IBM Performance Reports) it said "using xPath and navigating to the FIRST element", e.g. "//myElement[1]/anotherElement[1]/..."
This is kind of the only performant xpath expression there is. And it is not what you will need/use on projects.
The perf reports for Broker 6.x contains the stylesheet used (with "(xslt's) for each" and with "list[1]/Quantity" which is probably the best way to write a performant stylesheet).
Thought the stylesheet used is not included in the reports for Broker 7 and 8. (removed for what reason?)
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
