Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jul 5, 2010

UML-to-WSDL tranformation: meaningful fault names

Trying to achieve:
*Add named exceptions/faults to an interface operation in the model
*Run UML-to-WSDL and get a WSDL with operations/faults/fault messages

Current approach:
1. Start with an interface with an operation that has input/output
message defined
2. Add a parameter, set name to for example "PersonNotFound", set
direction "out"
3. Press the parameter, go to Advanced tab and set "Is Exception" to
4. Run transformation
Current result:
* The fault is added, but the fault message does not have
"PersonNotFound" in the name, but rather
* When using WSDL2Java or wsimport, the message name is used, which is
very cryptic
Proposed solution:
*Generate fault message name based on the pattern _ instead of _fault

Idea priority High
RFE ID 6524
RFE Product Rational Software Architect for WebSphere
  • Guest
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Software Architect for WebSphere

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Software Architect for WebSphere

  • Guest
    Oct 19, 2010

    This enhancement request is under consideration for a future release.

  • Guest
    Jul 14, 2010

    We will consider this enhancement request as an uncommitted candidate for a future release.

  • Guest
    Jul 7, 2010

    Modeled Business faults in WSDL are a major SOA top down differentiator. This feature would allow for the Business Process to better express the expected outcomes for the interface.