[jira] [Created] (SLING-5994) Move from Deprecated EventHandler to new ResourceChangeListener API
Hanish Bansal created SLING-5994: Summary: Move from Deprecated EventHandler to new ResourceChangeListener API Key: SLING-5994 URL: https://issues.apache.org/jira/browse/SLING-5994 Project: Sling Issue Type: Task Components: API Reporter: Hanish Bansal This issue serves as the container for the issues for migrating all implementations of EventHandler to new Resource Observation API in Sling Code. The new API that listens to the resource events is : https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java API for the Resource Change Events : https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5995) IdMapService should move to new ResourceChangeListener API
Hanish Bansal created SLING-5995: Summary: IdMapService should move to new ResourceChangeListener API Key: SLING-5995 URL: https://issues.apache.org/jira/browse/SLING-5995 Project: Sling Issue Type: Task Components: Extensions Reporter: Hanish Bansal org.apache.sling.discovery.commons.providers.spi.base.IdMapService currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5996) DistributedEventSender should move to new ResourceChangeListener API
Hanish Bansal created SLING-5996: Summary: DistributedEventSender should move to new ResourceChangeListener API Key: SLING-5996 URL: https://issues.apache.org/jira/browse/SLING-5996 Project: Sling Issue Type: Task Components: Extensions Reporter: Hanish Bansal org.apache.sling.event.dea.impl.DistributedEventSender currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5997) JobManagerImpl should move to new ResourceChangeListener API
Hanish Bansal created SLING-5997: Summary: JobManagerImpl should move to new ResourceChangeListener API Key: SLING-5997 URL: https://issues.apache.org/jira/browse/SLING-5997 Project: Sling Issue Type: Task Components: Extensions Reporter: Hanish Bansal org.apache.sling.event.impl.jobs.JobManagerImpl currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5998) NewJobSender should move to new ResourceChangeListener API
Hanish Bansal created SLING-5998: Summary: NewJobSender should move to new ResourceChangeListener API Key: SLING-5998 URL: https://issues.apache.org/jira/browse/SLING-5998 Project: Sling Issue Type: Task Reporter: Hanish Bansal org.apache.sling.event.impl.jobs.notifications.NewJobSender currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5999) JcrResourceBundleProvider should move to new ResourceChangeListener API
Hanish Bansal created SLING-5999: Summary: JcrResourceBundleProvider should move to new ResourceChangeListener API Key: SLING-5999 URL: https://issues.apache.org/jira/browse/SLING-5999 Project: Sling Issue Type: Task Components: Extensions Reporter: Hanish Bansal org.apache.sling.i18n.impl.JcrResourceBundleProvider currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6000) MapEntries should move to new ResourceChangeListener API
Hanish Bansal created SLING-6000: Summary: MapEntries should move to new ResourceChangeListener API Key: SLING-6000 URL: https://issues.apache.org/jira/browse/SLING-6000 Project: Sling Issue Type: Task Components: ResourceResolver Reporter: Hanish Bansal org.apache.sling.resourceresolver.impl.mapping.MapEntries currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6001) ProcessorManagerImpl should move to new ResourceChangeListener API
Hanish Bansal created SLING-6001: Summary: ProcessorManagerImpl should move to new ResourceChangeListener API Key: SLING-6001 URL: https://issues.apache.org/jira/browse/SLING-6001 Project: Sling Issue Type: Task Components: Extensions Reporter: Hanish Bansal org.apache.sling.rewriter.impl.ProcessorManagerImpl currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6002) ScriptCacheImpl should move to new ResourceChangeListener API
Hanish Bansal created SLING-6002: Summary: ScriptCacheImpl should move to new ResourceChangeListener API Key: SLING-6002 URL: https://issues.apache.org/jira/browse/SLING-6002 Project: Sling Issue Type: Task Components: Scripting Reporter: Hanish Bansal org.apache.sling.scripting.core.impl.ScriptCacheImpl currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6003) JavaScriptEngineFactory should move to new ResourceChangeListener API
Hanish Bansal created SLING-6003: Summary: JavaScriptEngineFactory should move to new ResourceChangeListener API Key: SLING-6003 URL: https://issues.apache.org/jira/browse/SLING-6003 Project: Sling Issue Type: Task Components: Scripting Reporter: Hanish Bansal org.apache.sling.scripting.java.impl.JavaScriptEngineFactory currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6004) JspScriptEngineFactory should move to new ResourceChangeListener API
Hanish Bansal created SLING-6004: Summary: JspScriptEngineFactory should move to new ResourceChangeListener API Key: SLING-6004 URL: https://issues.apache.org/jira/browse/SLING-6004 Project: Sling Issue Type: Task Components: Scripting Reporter: Hanish Bansal org.apache.sling.scripting.jsp.JspScriptEngineFactory currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6005) UnitChangeMonitor should move to new ResourceChangeListener API
Hanish Bansal created SLING-6005: Summary: UnitChangeMonitor should move to new ResourceChangeListener API Key: SLING-6005 URL: https://issues.apache.org/jira/browse/SLING-6005 Project: Sling Issue Type: Task Components: Scripting Reporter: Hanish Bansal org.apache.sling.scripting.sightly.impl.compiler.UnitChangeMonitor currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6006) SlingServletResolver should move to new ResourceChangeListener API
Hanish Bansal created SLING-6006: Summary: SlingServletResolver should move to new ResourceChangeListener API Key: SLING-6006 URL: https://issues.apache.org/jira/browse/SLING-6006 Project: Sling Issue Type: Task Components: Servlets Reporter: Hanish Bansal org.apache.sling.servlets.resolver.internal.SlingServletResolver currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-6007) XSSFilterImpl should move to new ResourceChangeListener API
Hanish Bansal created SLING-6007: Summary: XSSFilterImpl should move to new ResourceChangeListener API Key: SLING-6007 URL: https://issues.apache.org/jira/browse/SLING-6007 Project: Sling Issue Type: Task Components: XSS Protection API Reporter: Hanish Bansal org.apache.sling.xss.impl.XSSFilterImpl currently implements org.osgi.service.event.EventHandler Interface. We should start using the new ResourceChangeListener API. See [0] for details : https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5994) Move from EventHandler to new ResourceChangeListener API
[ https://issues.apache.org/jira/browse/SLING-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-5994: - Summary: Move from EventHandler to new ResourceChangeListener API (was: Move from Deprecated EventHandler to new ResourceChangeListener API) > Move from EventHandler to new ResourceChangeListener API > > > Key: SLING-5994 > URL: https://issues.apache.org/jira/browse/SLING-5994 > Project: Sling > Issue Type: Task > Components: API >Reporter: Hanish Bansal > > This issue serves as the container for the issues for migrating all > implementations of EventHandler to new Resource Observation API in Sling Code. > The new API that listens to the resource events is : > https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChangeListener.java > API for the Resource Change Events : > https://github.com/apache/sling/blob/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/observation/ResourceChange.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-5998) NewJobSender should move to new ResourceChangeListener API
[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469940#comment-15469940 ] Hanish Bansal commented on SLING-5998: -- Attaching a diff patch which fixes this issue "diff_SLING-5998.txt" > NewJobSender should move to new ResourceChangeListener API > -- > > Key: SLING-5998 > URL: https://issues.apache.org/jira/browse/SLING-5998 > Project: Sling > Issue Type: Task >Reporter: Hanish Bansal > Attachments: diff_SLING-5998.txt > > > org.apache.sling.event.impl.jobs.notifications.NewJobSender currently > implements org.osgi.service.event.EventHandler Interface. We should start > using the new ResourceChangeListener API. > See [0] for details : > https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-5998) NewJobSender should move to new ResourceChangeListener API
[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-5998: - Attachment: diff_SLING-5998.txt > NewJobSender should move to new ResourceChangeListener API > -- > > Key: SLING-5998 > URL: https://issues.apache.org/jira/browse/SLING-5998 > Project: Sling > Issue Type: Task >Reporter: Hanish Bansal > Attachments: diff_SLING-5998.txt > > > org.apache.sling.event.impl.jobs.notifications.NewJobSender currently > implements org.osgi.service.event.EventHandler Interface. We should start > using the new ResourceChangeListener API. > See [0] for details : > https://issues.apache.org/jira/browse/SLING-5994 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-2534) Strings of zero length on update in post servlet delete the property
[ https://issues.apache.org/jira/browse/SLING-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-2534: - Attachment: SLING-2534-diff.txt > Strings of zero length on update in post servlet delete the property > > > Key: SLING-2534 > URL: https://issues.apache.org/jira/browse/SLING-2534 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Post 2.1.2 >Reporter: Endolf >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Servlets Post 2.3.26 > > Attachments: SLING-2534-diff.txt, blankstrings.patch > > > According to JCR specs, for string type properties, a blank string should be > a valid value. Currently the post servlet delets any property where 1 or less > values are specifed and the 1 value has a 0 length. I think string properties > with a zero length should be blanked instead of deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-2534) Strings of zero length on update in post servlet delete the property
[ https://issues.apache.org/jira/browse/SLING-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-2534: - Attachment: (was: SLING-2534-diff.txt) > Strings of zero length on update in post servlet delete the property > > > Key: SLING-2534 > URL: https://issues.apache.org/jira/browse/SLING-2534 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Post 2.1.2 >Reporter: Endolf >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Servlets Post 2.3.26 > > Attachments: blankstrings.patch > > > According to JCR specs, for string type properties, a blank string should be > a valid value. Currently the post servlet delets any property where 1 or less > values are specifed and the 1 value has a 0 length. I think string properties > with a zero length should be blanked instead of deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-2534) Strings of zero length on update in post servlet delete the property
[ https://issues.apache.org/jira/browse/SLING-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanish Bansal updated SLING-2534: - Attachment: SLING-2534-diff.txt > Strings of zero length on update in post servlet delete the property > > > Key: SLING-2534 > URL: https://issues.apache.org/jira/browse/SLING-2534 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Post 2.1.2 >Reporter: Endolf >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Servlets Post 2.3.26 > > Attachments: SLING-2534-diff.txt, blankstrings.patch > > > According to JCR specs, for string type properties, a blank string should be > a valid value. Currently the post servlet delets any property where 1 or less > values are specifed and the 1 value has a 0 length. I think string properties > with a zero length should be blanked instead of deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-2534) Strings of zero length on update in post servlet delete the property
[
https://issues.apache.org/jira/browse/SLING-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709701#comment-16709701
]
Hanish Bansal commented on SLING-2534:
--
[~cziegeler] I have provided an updated patch on top of latest master -
{{SLING-2534-diff.txt}}
> Strings of zero length on update in post servlet delete the property
>
>
> Key: SLING-2534
> URL: https://issues.apache.org/jira/browse/SLING-2534
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Post 2.1.2
>Reporter: Endolf
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Servlets Post 2.3.26
>
> Attachments: SLING-2534-diff.txt, blankstrings.patch
>
>
> According to JCR specs, for string type properties, a blank string should be
> a valid value. Currently the post servlet delets any property where 1 or less
> values are specifed and the 1 value has a 0 length. I think string properties
> with a zero length should be blanked instead of deleted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
