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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Jan 2, 2015

RELATED IDEAS

Message Model Wizard, XSD hierarchy issue

"New Message Model" wizard... Two XML Options are provided: Option 1 "SOAP XML" i.e. use a WSDL, Option 2 "Other XML" e.g. use an XSD.

When importing from a pre-existing WSDL (Option 1) - you can successfully refer to the WSDL file and all dependent XSDs are also pulled into the Mesage Model automatically. This is good - it works just as well as the former Message Set import wizard in Message Broker.

When importing from a pre-existing XSD (Option 2) - There are two issues:

Issue 1) You can only select one XSD file at a time, dependent XSDs are not imported into the Message Model. This is inconsistent with the behavior exhibited when importing a WSDL file.

Issue 2) XSDs stored in a hierarchical package structure (with a
hierarchical namespace or file-system directory definition) are flattened, all XSDs are imported into the base project directory and are left broken (import / include statements are not updated to reflect the new XSD locations). This behavior has regressed in comparison to Message Broker Message Sets, where the Message Set import wizard would ensure that the organisational hierarchy of an XSD is preserved on-import.

Idea priority Urgent
RFE ID 63935
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Mar 11, 2021

    RFE Review. As part of our standard process for reviewing RFEs we have recently discussed this RFE and wish to note that it remains of long term interest to us. It is regrettable that we have not yet managed to prioritize this requirement for immediate action, but we will continue to monitor for popularity and keep it in mind for future plans. Status is maintained as Uncommitted Candidate.

  • Guest
    Reply
    |     Oct 7, 2015

    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

  • Guest
    Reply
    |     Jan 5, 2015

    Fully understand the problem, but meantime here is a workaround that might help.

    If you wrap the root xsd in a skeletal wsdl then import the wsdl, the xsds get imported in the correct folders.

    Here's an example skeletal wsdl for a root xsd called PhoneBanking.xsd in namespace http://www.example.com/PhoneBanking. The wsdl only needs to contain the wsdl:types section (to import the root xsd), a wsdl:binding and an empty wsdl:types.


    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">










  • Guest
    Reply
    |     Jan 2, 2015

    Attachment (Description)

    New Message Mod...
    New Message Model Wizard.png
    Open full size
    New Message Model Wizard.png

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.