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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Useful for anyone trying to migrate from tWAS to Liberty using ear files with mainfest class path outside WAR.
Behavior difference between WAS traditional and Liberty regarding the handling of WAR manifest class paths. In WAS traditional, class path entries in a web module's manifest are added to the EAR class loader; in Liberty, they're added to the WAR class loader.
Idea priority | Low |
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.
We have released an implementation of this Idea into the Open Liberty 24.0.0.11-beta with https://github.com/OpenLiberty/open-liberty/issues/28110
You can see a preview of the upcoming beta blog about this functionality in
https://github.com/OpenLiberty/open-liberty/issues/29766
Short version:
To enable the functionality you add the attribute webModuleClassPathLoader="ear" to the enterpriseApplication configuration in the Liberty server's configuration file server.xml. For example, like the following:
Note that you must use the <enterpriseApplication/> configuration to enable this functionality. This implies that you cannot deploy the application EAR to the Liberty dropins/ folder.
Thanks for the feature request, and we look forward to hearing your feedback on the beta functionality.