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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/05/01 16:22:17 UTC
[jira] [Commented] (OAK-775) Implement backward compatible
observation
[ https://issues.apache.org/jira/browse/OAK-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646614#comment-13646614 ]
Michael Dürig commented on OAK-775:
-----------------------------------
To better understand the backwards compatibility issues associated with observation in Oak, I added additional logging at revision 1478014:
* Each registered and re-registered observation listener is logged at debug level along with its filter parameters using the marker {{observation}}.
* Each call to {{Event.getUserId}} and {{Event.getUserData}} is logged at warning level using the marker {{deprecation}}.
> Implement backward compatible observation
> -----------------------------------------
>
> Key: OAK-775
> URL: https://issues.apache.org/jira/browse/OAK-775
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Attachments: OAK-775-isExternal.patch, OAK-775.patch
>
>
> As [discussed | http://markmail.org/message/6bqycmx6vbq7m25c] we might want look into implementing an alternative approach to observation, which trades some scalability for improved backward compatibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira