[jira] [Updated] (SLING-6164) Introduce optional property names hint to ResourceChangeListener

2016-10-17 Thread Stefan Egli (JIRA)

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

Stefan Egli updated SLING-6164:
---
Fix Version/s: Resource Resolver 1.5.0

> Introduce optional property names hint to ResourceChangeListener
> 
>
> Key: SLING-6164
> URL: https://issues.apache.org/jira/browse/SLING-6164
> Project: Sling
>  Issue Type: Improvement
>  Components: API, JCR
>Affects Versions: JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
>Reporter: Stefan Egli
> Fix For: JCR Resource 2.9.0, API 2.15.0, Resource Resolver 1.5.0
>
> Attachments: SLING-6164.patch
>
>
> As [discussed on the list|http://sling.markmail.org/thread/usq4a7pglhakd7uq] 
> it would be useful to allow resource providers to optionally filter for 
> property names for ResourceChangeListeners. We could thus introduce an 
> optional _property names hint_ osgi property to the ResourceChangeListener as 
> well as the corresponding getter to ObserverConfiguration.



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


[jira] [Updated] (SLING-6164) Introduce optional property names hint to ResourceChangeListener

2016-10-17 Thread Stefan Egli (JIRA)

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

Stefan Egli updated SLING-6164:
---
Affects Version/s: Resource Resolver 1.4.18

> Introduce optional property names hint to ResourceChangeListener
> 
>
> Key: SLING-6164
> URL: https://issues.apache.org/jira/browse/SLING-6164
> Project: Sling
>  Issue Type: Improvement
>  Components: API, JCR
>Affects Versions: JCR Resource 2.8.0, API 2.14.2, Resource Resolver 1.4.18
>Reporter: Stefan Egli
> Fix For: JCR Resource 2.9.0, API 2.15.0, Resource Resolver 1.5.0
>
> Attachments: SLING-6164.patch
>
>
> As [discussed on the list|http://sling.markmail.org/thread/usq4a7pglhakd7uq] 
> it would be useful to allow resource providers to optionally filter for 
> property names for ResourceChangeListeners. We could thus introduce an 
> optional _property names hint_ osgi property to the ResourceChangeListener as 
> well as the corresponding getter to ObserverConfiguration.



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


[jira] [Updated] (SLING-6164) Introduce optional property names hint to ResourceChangeListener

2016-10-17 Thread Stefan Egli (JIRA)

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

Stefan Egli updated SLING-6164:
---
Attachment: SLING-6164.patch

Attached [^SLING-6164.patch] with a suggestion for the API change as well as 
the corresponding (no-op) implementation in JCR Resource.
/cc [~cziegeler], [~chetanm]

> Introduce optional property names hint to ResourceChangeListener
> 
>
> Key: SLING-6164
> URL: https://issues.apache.org/jira/browse/SLING-6164
> Project: Sling
>  Issue Type: Improvement
>  Components: API, JCR
>Affects Versions: JCR Resource 2.8.0, API 2.14.2
>Reporter: Stefan Egli
> Fix For: JCR Resource 2.9.0, API 2.15.0
>
> Attachments: SLING-6164.patch
>
>
> As [discussed on the list|http://sling.markmail.org/thread/usq4a7pglhakd7uq] 
> it would be useful to allow resource providers to optionally filter for 
> property names for ResourceChangeListeners. We could thus introduce an 
> optional _property names hint_ osgi property to the ResourceChangeListener as 
> well as the corresponding getter to ObserverConfiguration.



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