Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How are SessionScoped beans supposed to work with java.lang.Optional?
See original GitHub issueCurrently it does not seem possible to have optional values for session scopes CDI beans?!
According to: https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configexamples.asciidoc
someone always have to provide a default value.
==> Optional is not Serializable
Also this usage of Optional is questionable:
void method(@ConfigProperty(name = "a.config.key") final Optional<String> value)){...}
Optional should be used for return types only!
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for your reply. I think this should be mentioned in the documentation. E.g. in the mentioned example: https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configexamples.asciidoc
Cheers
@svenhaag The optionality is for some properties that might have not got value assigned. The best practices is that you should provide default value. If you do need to have optional value, you can use programmatic lookup e.g.
ConfigProvider.getConfig.getOptionalValue()instead of injection on yourSessionScopedorConversationScopedor any other passivation scoped beans.The injection for the type
Optionalis fine for non passivation scoped beans though.