Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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.

Status Delivered
Categories EGL Language
Created by Guest
Created on Nov 17, 2014

WSDL client interface on nillable fields can't be compared to null

When I create a client interface from a web service wsdl files for a record which contains nillable fields, the record field can not be compared to null.
It always defaults to the current date.

The client interface record has the following parameter:
{@XMLElement{nillable=true}}
If I remove this from the generated record, the field can be compared to null.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 21, 2015

    This feature was delivered in version 9.5.

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Business Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Business Developer

  • Guest
    Reply
    |
    Jan 3, 2015

    Thank you for this suggestion. We think it is a good idea, and we will consider it when we are planning for our next release

  • Guest
    Reply
    |
    Dec 5, 2014

    Attachment (Use case): The project displaying the issue. I have removed the libraries in the service project to reduce the size.

  • Guest
    Reply
    |
    Dec 5, 2014

    My previous explanation was not 100% correct. The issue is shown in the attached project files.

    The project has a service side and a rui side.
    There are two identical records retrieved by the service (RecOk and RecFail).
    I have adapted the client interface of the "recFail" record. (removed the xmlnillable parameter)

    The recFail can be compared to null, the recOk can't.

    So in summary: the issue does not occur on nullable integer or date fields, but it does on nullable sub-records.

    Kind regards,

    Bram

  • Guest
    Reply
    |
    Dec 3, 2014

    We try this scenario, the generated field is nullable type(int?). We cannot find the problem you mentioned. Please provide more information to reproduce the problem. Thanks.