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 ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Dec 9, 2020

Liberty thin client for JMS

Our product uses the JMS support within Liberty to publish messages that can be subscribed to by clients (Eclipse plug-in or Ant build) to get feedback on long running processes. Currently we rely on the WAS thin client for JMS to provide this capability with our clients but this creates an otherwise unnecessary dependency on WAS when all we are using from it is that thin client jar and the rest of our application runs entirely within a Liberty server.

In addition, recent Eclipse releases (e.g. 2020-09) require a minimum of Java 11. However, the WAS thin client for JMS depends on the ORB classes supplied within Java which presents a problem as since Java 11 these APIs have been dropped from Java SE (JEP 320).

It would be great if Liberty could supply an equivalent thin client for JMS that we could use within clients running Java 11 to communicate with a JMS topic hosted by a Liberty server.

Use Case
Our Eclipse and Ant clients provide real time feedback on server processes via an Eclipse console or stdout respectively. The Eclipse plug-in also uses the JMS publish/subscribe model to monitor status and activity of some of our components running within the Liberty server.
RFE ID 147292
RFE URL
RFE Product WebSphere Application Server
Idea Priority Medium