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.
RFE Review. Further to the last comment on this idea, and as part of our policy for regularly reassessing aged RFEs, we have recently discussed this enhancement request again and unfortunately on this occasion it has been decided that we won't be taking this idea further forward. Given the existence of other potential workarounds, the functional area of web servies WSDL importing not being under active development right now, and having received only 2 votes over its 8 year lifespan, I'm afraid we are unable to prioritise action on this item at this time. Status of the idea is closed.
RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. The key consideration with this enhancment request is the degree to which the Toolkit should offer more detailed options for the user to select what they would like to happen when they want to update some metadata but not necessarily all of its dependencies. As noted, when importing WSDL, frequently you might have associated XSD content, which in some cases you may wish to separate into other library projects which may or may not be present in your local workspace. If you wish to reimport your WSDL, you could do this, and then discard the schemas if you knew they had not changed ... There is an argument that the analysis of whether the dependent schemas are the same as a set that have previously been imported should be the job of the Toolkit rather than the user ... but equally this could be passed on to your SCM tool, or to your version control repository tool. In summary, we do not see this as an urgent need, but acknowledge that there could be improvements in behaviour in this area. Given this, we note that this RFE has only gathered 2 votes over the last six years, so this is unlikely to be prioritized soon, but we will certainly continue to monitor. Status of the RFE is updated to Uncommitted Candidate.
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
Hello,
I see already some changes in IIB 9.0.0.2 which is already a step in the right direction. The XSDs are no longer copied to a dir structure reflecting the namespace. The dir structure from the input is copied but not alwas correct.
In the lib we have a dir Schema with the subdirs CDM and Services. The WSDL is lower in the Services directory. After import the XSDs are copied to dirs CDM and Services direct under the Lib project.
When I place the CMD and Services dirs direct in the project (without the Schema dir), the result is the same. I guess the dir structure is now created fomr the relative pahts in the WSDL and XSDs.
There is now an other problme with the WSDL file. With the import a new WSDL file is created direct under the project. However the old WSDL is still in the subdir and is marked in error because it is not 'imported'.
This RFE is related to RFE 53555.