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 Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Jul 31, 2018

RELATED IDEAS

Unspecific error thrown by "validation" policy in API Management

Please refer to the ticket: TS001157822 for more information.

https://www.ibm.com/mysupport/s/case/500500000188rvnAAA/unable-to-validate-json-keys-with-swagger-definition-using-validate-policy



I am copying below a message from IBM support team which referred us to open RFE.

"kajagana (IBM)
24 Jul 2018 10:23 AM
Hello Ankit,

I have discussed this with our extended team in detail. I am getting an understanding that this error message is thrown from DataPower and it is working as designed. From your viewpoint I understand that the error message is not specific and may not be helpful. If you think that the error message needs to updated, then the enhancement of this validation error message in the case of additionalProperties with a value of false will require a RFE. You should open using https://www.ibm.com/developerworks/rfe/execute?use_case=changeRequestLanding and should specify DataPower as the product.

Please let us know if any related questions. If none, please provide permission to close the

case. Thanks.

with regards

Jag"

Idea priority High
RFE ID 123087
RFE URL
RFE Product IBM DataPower Gateways
  • Admin
    CHRISTOPHER KHOURY
    Reply
    |     Sep 20, 2022

    Thank you for your input. The messages are correct and while understandably not as detailed as your would like we consider the gateway to be primarily a runtime in this case and we would recommend customers utilized development tooling to assist in more detailed debugging.

  • Guest
    Reply
    |     Aug 26, 2022

    IBM API Connect provides terrible error messages in general for the Errors thrown to the Catch block. The Validate policy is the worst with the cryptic JSV001, JSV006 messages that don't provide any detail. Just adding the JSON field property name to the error message would go a long way.

  • Guest
    Reply
    |     Feb 22, 2022

    Hi,

    I would like this case to return being under consideration.

    This error message needs to be updated. I don't understand why I should open a different RFE, because this RFE's product is already "IBM DataPower Gateways".

    By the way, the error is unclear not only in the case of "additionalProperties=false", but in many other cases.

    For example, if there's an enum in the schema, the error for sending a value which is not a part of the enum looks like this: "[JSV0013] Invalid value: the value is not among the permitted enumerated value". Once again, it doesn't state what is the value, what is the enum, what field caused it. If I have several fields which are defined with enums, I have no idea which of those field got an illegal value and what was that value.

    There are many more unclear errors, just like this in terms of JSON validation.

    Thanks,

    Shahar.

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.