Am 01.10.2017 um 16:15 schrieb Oliver B. Fischer: > Hm, looking at the code now I think you are right that is doesn't make > such sense.
Thanks for all of your opinions - I was opposed to the optional stuff because I try to see it from a semantic point of view. What is an optional-empty configuration value? Does it mean the value is optional or does it mean the customer forgot to configure it properly. How do I distinguish these two situations. To my mind this would make the API less clear. Therefore I prefer the getOrDefault()-approach instead. Talking to Oliver at Bedcon he pointed out that Optional might make it easier for clients to do proper error handling .... @John: do you have an example that might make it easier and more concise why we want to have optional. Thanks, Phil
