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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
LIBERTY and configuration validation when starting
1) Liberty read configuration from server.xml But if it exists bad configuration it will start without any fatal errors. (ignore the xml that liberty does not understand) It is a kind of “best effort” starting that I do not want. I prefer that It does not start and said “bad configuration with …”. If not it will not have the behavior that we expect to be.
may be we can add a switch to have a strict validation of the xml configuration when starting ?
2) Can we see the effective “in memory” configuration ?
examples: ** If you declare Two registries it will federate both. So there is implicit configuration inside the runtime I‘d like to see this somewhere.
** if you read multiples files (include xml, configuration dropins…) , I want to see the “in memory result configuration tree” I‘d like to see the server.xml with all the configuration that is currently in memory.
Do not place IBM confidential, company confidential, or personal information into any field.