Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Do you have any new information?
For general FYI, as part of our regular practice of reviewing RFEs this enhancement remains on our radar. Status currently kept at Uncommitted Candidate.
May I ask You, if there is any progress with the support of XSL-T 3.0 and XPath 3.1 in ACE 11?
TIBCO and WSO2 have a support for XSLT 2.0, Mule has even support of XSLT 3.0 and XPath 3.1...
Now, when XSL-T 2.0 is almost overcome with XSL-T 3.0 and XPath 3.1, whould not be better to skip support of XSL-T 2.0 and XPath 2.0 and move forward the effort to the support of XSL-T 3.0 and XPath 3.1? What about to allow to use Saxon HE, PE, EE or Exselt engines as the XSL-T engines for XSL-T transformation?
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Support for this is long overdue.
I think, that request # 47235 is not duplicated to this request # 53855. This one is about XPath 2.0, while that one is about XSL-T 2.0. And also I think, that we would like to have read and write access to the whole Root via XSL-T 2.0, not only current Body (so to add Properties, Environment, LocalEnvironment...). And IBM has its own implementation of XSL-T 2.0 engine (IBM WebSphere Application Server V7.0 Feature Pack for XML) for years, so...
Thanks; we'll add XPATH 2.0 support in due course.