You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Vidar S. Ramdal (JIRA)" <ji...@apache.org> on 2010/03/24 15:40:27 UTC
[jira] Created: (SLING-1463) Rewrite MapEntries to be a OSGi
EventHandler instead of a JCR EventListener
Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
---------------------------------------------------------------------------
Key: SLING-1463
URL: https://issues.apache.org/jira/browse/SLING-1463
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Vidar S. Ramdal
Fix For: JCR Resource 2.0.8
o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1463) Rewrite MapEntries to be a OSGi
EventHandler instead of a JCR EventListener
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson updated SLING-1463:
----------------------------------
Fix Version/s: (was: JCR Resource 2.0.8)
descheduling from current release
> Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
> ---------------------------------------------------------------------------
>
> Key: SLING-1463
> URL: https://issues.apache.org/jira/browse/SLING-1463
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Vidar S. Ramdal
> Assignee: Carsten Ziegeler
> Attachments: SLING1463.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
> Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
> To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
> As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
> Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1463) Rewrite MapEntries to be a OSGi
EventHandler instead of a JCR EventListener
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1463:
------------------------------------
Attachment: SLING1463.patch
Proposed patch (haven't tested it yet)
> Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
> ---------------------------------------------------------------------------
>
> Key: SLING-1463
> URL: https://issues.apache.org/jira/browse/SLING-1463
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Vidar S. Ramdal
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.0.8
>
> Attachments: SLING1463.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
> Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
> To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
> As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
> Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1463) Rewrite MapEntries to be a OSGi
EventHandler instead of a JCR EventListener
Posted by "Vidar S. Ramdal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vidar S. Ramdal updated SLING-1463:
-----------------------------------
Description:
o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf
was:
o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
> Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
> ---------------------------------------------------------------------------
>
> Key: SLING-1463
> URL: https://issues.apache.org/jira/browse/SLING-1463
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Vidar S. Ramdal
> Fix For: JCR Resource 2.0.8
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
> Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
> To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
> As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
> Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1463) Rewrite MapEntries to be a OSGi
EventHandler instead of a JCR EventListener
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-1463:
---------------------------------------
Assignee: Carsten Ziegeler
> Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
> ---------------------------------------------------------------------------
>
> Key: SLING-1463
> URL: https://issues.apache.org/jira/browse/SLING-1463
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Vidar S. Ramdal
> Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.0.8
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map.
> Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener.
> To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener.
> As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard.
> Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.