[
https://issues.apache.org/jira/browse/SLING-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142083#comment-17142083
]
Jörg Hoh commented on SLING-8706:
---------------------------------
[~jmanuelbr] Using Java Optionals would be just another way to express the
fact, that a certain field might not be present. You still can change the
overall strategy or annotate any field individually with {{@Optional}}, the
current behavior and the way annotations are working must not change.
> Injections for java.util.Optional<> should be automatic optional
> -----------------------------------------------------------------
>
> Key: SLING-8706
> URL: https://issues.apache.org/jira/browse/SLING-8706
> Project: Sling
> Issue Type: Improvement
> Components: Sling Models
> Reporter: Jörg Hoh
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The current approach to support optional injections requires to annotate the
> field with {{@Optional}} plus proper handling within the javacode (null
> checks etc), which can be forgotten.
> So instead of
> {code}
> @Inject @Optional
> String fieldname;
> {code}
> it should also be possible to use this
> {code}
> @Inject
> Optional<String> fieldname;
> {code}
> with the very same semantic. But the developer is forced to deal with the
> case that the value is not present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
