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.
Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. The MbXPath class operates on the logical tree and helps flow developers to navigate through logical tree structures. We understand that taking advantage of XPath 2.0 functions would further expand these capabilities, and we agree that this would increase the power of flow transformation functions such as the graphical mapper / JavaCompute node etc. Given the slight diversion in previous comments about JSON, it is also worth noting that more recent versions of the product support the modelling, validation and mapping of JSON formats in the graphical mapper. Regarding the core of the request here, we would like to note that unfortunately this remains a low business priority for us ... we're sure this will not be a surprise given the long time period this request has been open and the single community vote that it has received. That said, we would like to maintain the status as Future Consideration for potential future implementation.
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
OK, thanks for the clarification.
(XPath 2.0 support in JCN) != (JSON support in GDM). I think JSON support in GDM is higher priority. I think XPath 2.0 in JCN would be nice to have, so I marked it low priority.
Thanks for raising the requirement. I'd like to understand the core of what's needed - e.g. if we added JSON support to the GDM would that resolve the requirement?