[jira] [Commented] (SLING-4895) Service registry should not be called from within synchronized block

[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640018#comment-14640018 ] Carsten Ziegeler commented on SLING-4895: - I think the easiest solution is to queu

[jira] [Updated] (SLING-4893) Service already unregistered exception in ScriptCacheImpl

[ https://issues.apache.org/jira/browse/SLING-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4893: Fix Version/s: Scripting Core 2.0.32 > Service already unregistered exception in ScriptCacheImpl > -

[jira] [Updated] (SLING-4893) Service already unregistered exception in ScriptCacheImpl

[ https://issues.apache.org/jira/browse/SLING-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4893: Affects Version/s: (was: Scripting Core 2.0.28) Scripting Core 2.0.30 > S

[jira] [Resolved] (SLING-4893) Service already unregistered exception in ScriptCacheImpl

[ https://issues.apache.org/jira/browse/SLING-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4893. - Resolution: Duplicate > Service already unregistered exception in ScriptCacheImpl > --

Re: Resource Resolvers in OSGi Service APIs

Am 23.07.15 um 18:19 schrieb Konrad Windszus: > For Sling Validation I just came across the issue that I need a resource > resolver in the implementation (e.g. for triggering a search to find the > validation models in the repository or to figure out the resource super type). > Currently the API

[jira] [Updated] (SLING-4900) Clarify javadoc on ResourceResolver.getParentResourceType(String)

[ https://issues.apache.org/jira/browse/SLING-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4900: Affects Version/s: (was: Resource Resolver 1.2.6) API 2.9.0 > Cla

[jira] [Commented] (SLING-4788) SlingConfigurationPrinter should use mode aware and only stream the full logs in the zip version and avoid duplicate information

[ https://issues.apache.org/jira/browse/SLING-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639956#comment-14639956 ] Carsten Ziegeler commented on SLING-4788: - I think the inventory api is there for

[jira] [Commented] (SLING-2622) Framework does not log through the Sling Logging Infrastructure

[ https://issues.apache.org/jira/browse/SLING-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639954#comment-14639954 ] Carsten Ziegeler commented on SLING-2622: - I think this is somehow possible, afaik

[jira] [Resolved] (SLING-4850) MockValueMap should implement containsKey

[ https://issues.apache.org/jira/browse/SLING-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-4850. --- Resolution: Fixed Completed: At revision: 1692454 should be fixed > MockValueMap should im

[jira] [Updated] (SLING-4850) MockValueMap should implement containsKey

[ https://issues.apache.org/jira/browse/SLING-4850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-4850: -- Assignee: Stefan Seifert Affects Version/s: Testing ResourceResolver Mock 1.1.6

[jira] [Resolved] (SLING-4901) osgi-mock: Add support for ComponentContext.getUsingBundle()

[ https://issues.apache.org/jira/browse/SLING-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-4901. --- Resolution: Fixed Completed: At revision: 1692452 > osgi-mock: Add support for ComponentCo

[jira] [Created] (SLING-4901) osgi-mock: Add support for ComponentContext.getUsingBundle()

Stefan Seifert created SLING-4901: - Summary: osgi-mock: Add support for ComponentContext.getUsingBundle() Key: SLING-4901 URL: https://issues.apache.org/jira/browse/SLING-4901 Project: Sling

Resource Resolvers in OSGi Service APIs

For Sling Validation I just came across the issue that I need a resource resolver in the implementation (e.g. for triggering a search to find the validation models in the repository or to figure out the resource super type). Currently the API is designed that no resolver is passed when any servic

Re: [vote] Accept the contribution of Log Tail Plugin tracked in SLING-4897

+1 Chetan Mehrotra On Wed, Jul 22, 2015 at 7:45 PM, Varun Nagpal wrote: > Hi, > > This thread is about voting for the acceptance of the Log Tail Plugin > tracked in SLING-4897. > > An archive (sling-logtail.zip, md5sum 6d14f2ef4748c00e63cbbaeda7224e3c) > containing the contribution is attached t

[jira] [Updated] (SLING-4900) Clarify javadoc on ResourceResolver.getParentResourceType(String)

[ https://issues.apache.org/jira/browse/SLING-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4900: --- Description: Currently the javadoc for {{ResourceResolver.getParentResourceType(String)}} is

[jira] [Created] (SLING-4900) Clarify javadoc on ResourceResolver.getParentResourceType(String)

Konrad Windszus created SLING-4900: -- Summary: Clarify javadoc on ResourceResolver.getParentResourceType(String) Key: SLING-4900 URL: https://issues.apache.org/jira/browse/SLING-4900 Project: Sling

[jira] [Created] (SLING-4899) Background servlet not cluster aware

Marcel Reutegger created SLING-4899: --- Summary: Background servlet not cluster aware Key: SLING-4899 URL: https://issues.apache.org/jira/browse/SLING-4899 Project: Sling Issue Type: Bug