Just in case you did not know this already -
I was able to execute XSLT 2.0 transformations on ORABPEL 10.1.3.1 runtime.
Even though the graphical modeler does not support this, I could actually design and develop XSLT 2.0 transformation code.
XSLT 2.0 has significant advantages over 1.0 .
Five XSLT 2.0 Features that simplify XML Document transformations - http://www.oracle.com/technology/pub/articles/wang_xslt.html
Whats new in XSLT 2.0 - http://www.xml.com/pub/a/2002/04/10/xslt2.html
XSLT 2.0 Specification - http://www.w3.org/TR/xslt20/
XQuery 1.0 and XPath Functions and Operators - http://www.w3.org/TR/xpath-functions/
XPath 2.0 Specification - http://www.w3.org/TR/xpath20/
You need to ensure that the version attribute on your stylesheet element in the XSLT has the value "2.0" to ensure that the XSLT 2.0 processor executes your transformation code.
« Passing BPEL Variable contents into XSLT as Parameters | Main | Setting the title of the BPEL Instance »
XSLT 2.0
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on May 21, 2007 7:30 PM.
The previous post in this blog was Passing BPEL Variable contents into XSLT as Parameters.
The next post in this blog is Setting the title of the BPEL Instance.
Many more can be found on the main index page or by looking through the archives.
Comments (1)
Hi Ramkumar,
Have you successfully tried using the replace() function, which is new in XPath2.0, in an XSL in BPEL 10.1.3.1 or above?
In my XSL, I changed xsl:stylesheet version="1.0" to xsl:stylesheet version="2.0" and tried to use the replace function, but was not successful. What am I missing?
Thanks for your help.
Posted by Eddie Awad | August 5, 2008 3:29 PM
Posted on August 5, 2008 15:29