You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2016/11/29 08:20:59 UTC

[jira] [Updated] (OAK-5160) change Nonnull to Nullable in FilteringAwareObserver.contentChanged

     [ https://issues.apache.org/jira/browse/OAK-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli updated OAK-5160:
-----------------------------
    Attachment: OAK-5160.patch

Attached [^OAK-5160.patch] as a suggestion to hold back the first content change (which corresponds to the {{before}} being null). [~mreutegg] wdyt?

> change Nonnull to Nullable in FilteringAwareObserver.contentChanged
> -------------------------------------------------------------------
>
>                 Key: OAK-5160
>                 URL: https://issues.apache.org/jira/browse/OAK-5160
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.5.14
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.6, 1.5.15
>
>         Attachments: OAK-5160.patch
>
>
> FilteringAwareObserver (and thus ChangeProcessor)'s {{contentChanged}} has {{@Nonnull}} for the {{before}} parameter. But for the very first contentChanged (at initialization time) this can actually be null. So we should change that to {{@Nullable}} there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)