Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

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.