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 Delivered
Workspace WebSphere Liberty
Created by Guest
Created on Feb 12, 2021

WLP 20.0.0.x EclipseLink DB2Platform no longer binds Literals as Parameters

EclipseLink DB2Platform no longer binds Literals as Parameters ( => this.shouldBindLiterals = false;)

We are using EclipseLink packaged within Websphere Liberty Profile (WLP) version 20.0.0.x in combination with DB2. WLP 20.0.0.x packages EclipseLink in the version 2.7.6.

While updating from WLP version 19.0.0.x to 20.0.0.x we experience problems with the new provided EclipseLink version 2.7.6. As changed in the DB2Platform with version 2.7.6 ( literals get no longer bound as parameters in the query when using Criteria Builder, literals are bound inline in the SQL-statements. This behaviour leads to changed SQL-statements and restricts DB2 to NO longer use prepared statements with parameters.

Changes that force DB2Platform to "this.shouldBindLiterals = false" were implemented with:

EclipseLink Issue: #492
EclipseLink Commit: 418a2e5
IBM related issue:
There exists another IBM related Issue (, but I am not sure if this IBM issue relates to my issue.

In general and independent of known workarounds, we ask for a global solution that allows to set the property "shouldBindLiterals" via system properties (similar to "eclipselink.jdbc.force-bind-parameters" and "eclipselink.jdbc.bind-parameters" => and L#2833). We are also open for other global solutions or fixes that allow us to bind literals as parameters!

For more information =>

Idea priority Medium
RFE ID 148566
RFE Product WebSphere Application Server