Re: searchPath based on content path + multitenancy

Bertrand Delacretaz wrote > On Thu, Mar 3, 2016 at 8:26 AM, Carsten Ziegeler wrote: >> ...I was thinking of rewriting the whole script resolution mechanism to >> have a better caching mechanism. Maybe if we do one of these things we >> look into the other as well :).. > > I

Re: searchPath based on content path + multitenancy

On Thu, Mar 3, 2016 at 8:26 AM, Carsten Ziegeler wrote: > ...I was thinking of rewriting the whole script resolution mechanism to > have a better caching mechanism. Maybe if we do one of these things we > look into the other as well :).. I think so - including some form of

Re: searchPath based on content path + multitenancy

Henry Saginor wrote > Thanks Bertrand, > I see that at Sling engine level ServletResolver is pluggable already. So, > this is something I could do at the project level as well. > Project level ServletResolver could still delegate to default > SlingServletResolver, I suppose, after resolving

Re: Random Failure to Deploy a File using AddOrUpdateNodeCommand

I went ahead and took out any changed resource that contains a path with /renditions/ but not /renditions/original That solves the issue if a workflow is present and active but, of course, if the workflow is not enabled then there will be no renditions. We could make it configurable to ignore

Re: Random Failure to Deploy a File using AddOrUpdateNodeCommand

Hi Robert Yes, the Workflow are the most likely culprit as I did not encounter a problem when the Workflow were disabled but as soon as I switched them back on the error was back. So I am wondering if the /renditions folder should be replicated at all. BTW the error occurs even if the

Re: [VOTE] release Health Checks Core 1.2.4 and Health Checks Annotations 1.0.4

+1 (non-binding) -Georg On 2016-03-02 15:43, Bertrand Delacretaz wrote: Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12332272 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1437 You can use

Re: searchPath based on content path + multitenancy

Thanks Bertrand, I see that at Sling engine level ServletResolver is pluggable already. So, this is something I could do at the project level as well. Project level ServletResolver could still delegate to default SlingServletResolver, I suppose, after resolving script name to absolute path or

Re: searchPath based on content path + multitenancy

Hi Jorg, Thank you for your input. I have considered using different resource types. This would work. But my use case is a bit different from true multi-tenancy. This is one company/tenant hosting their own Sling (CQ just upgraded to AEM 6.1) instances. They have been working on reimplementing

[jira] [Resolved] (SLING-3605) Debug based on bundles deployed on the server

[ https://issues.apache.org/jira/browse/SLING-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3605. Resolution: Fixed > Debug based on bundles deployed on the server >

[jira] [Commented] (SLING-3605) Debug based on bundles deployed on the server

[ https://issues.apache.org/jira/browse/SLING-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175901#comment-15175901 ] Robert Munteanu commented on SLING-3605: - [r1733325|https://svn.apache.org/r1733325] - print

[jira] [Updated] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5579: Assignee: (was: Carsten Ziegeler) > setActive is not set to true during activation of

[jira] [Updated] (SLING-4752) New resource query API

[ https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4752: Fix Version/s: (was: Resource Resolver 1.4.6) Resource Resolver 1.5.0

[jira] [Resolved] (SLING-5561) Resource Resolver Factory should be deactivated before provider is removed

[ https://issues.apache.org/jira/browse/SLING-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5561. - Resolution: Fixed > Resource Resolver Factory should be deactivated before provider is

[jira] [Updated] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5579: Fix Version/s: (was: Resource Resolver 1.5.0) > setActive is not set to true during

[jira] [Commented] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175826#comment-15175826 ] Konrad Windszus commented on SLING-5579: Just for the reference: OSGi Compendium, Release 6,

[jira] [Reopened] (SLING-3605) Debug based on bundles deployed on the server

[ https://issues.apache.org/jira/browse/SLING-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reopened SLING-3605: Reopening to address some minor usability issues > Debug based on bundles deployed on the

[jira] [Commented] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175779#comment-15175779 ] Marius Petria commented on SLING-5578: -- No problem :), just as an historical reference this issue is

[jira] [Closed] (SLING-5553) Start background servlet jobs for POST, PUT and DELETE only by default

[ https://issues.apache.org/jira/browse/SLING-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed SLING-5553. -- > Start background servlet jobs for POST, PUT and DELETE only by default >

[jira] [Commented] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175713#comment-15175713 ] Marius Petria commented on SLING-5578: -- The change is somehow trivial (just three lines of code

[jira] [Commented] (SLING-5561) Resource Resolver Factory should be deactivated before provider is removed

[ https://issues.apache.org/jira/browse/SLING-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175712#comment-15175712 ] Carsten Ziegeler commented on SLING-5561: - I've committed a first potential solution: - if a

[jira] [Commented] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175721#comment-15175721 ] Bertrand Delacretaz commented on SLING-5578: We should not have accepted that class without

[jira] [Closed] (SLING-5535) Background Job Web Console should use POST for job manipulation

[ https://issues.apache.org/jira/browse/SLING-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed SLING-5535. -- > Background Job Web Console should use POST for job manipulation >

[jira] [Closed] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

[ https://issues.apache.org/jira/browse/SLING-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed SLING-5227. -- > Remove loginAdministrative() usage from org.apache.sling.bgservlets >

[jira] [Updated] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-5578: - Attachment: SLING-5578.test.diff I attached a test for the current problem: a node with 20K

[jira] [Commented] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175695#comment-15175695 ] Bertrand Delacretaz commented on SLING-5578: Ok thanks, IMO we should have good test coverage

[VOTE] release Health Checks Core 1.2.4 and Health Checks Annotations 1.0.4

Hi, We solved 6 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12332272 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1437 You can use this UNIX script to download the release and verify the signatures:

[jira] [Assigned] (SLING-5561) Resource Resolver Factory should be deactivated before provider is removed

[ https://issues.apache.org/jira/browse/SLING-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5561: --- Assignee: Carsten Ziegeler > Resource Resolver Factory should be deactivated before

[jira] [Commented] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175669#comment-15175669 ] Santiago García Pimentel commented on SLING-5579: - [~cziegeler] could be. We got hit by

[jira] [Commented] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175652#comment-15175652 ] Carsten Ziegeler commented on SLING-5579: - I think the logic is correct as an instance of the

[jira] [Resolved] (SLING-5580) Resource Resolver Factory is wrongly activated when zero or more than one required providers

[ https://issues.apache.org/jira/browse/SLING-5580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5580. - Resolution: Fixed Correct the logic and added a set of unit tests verifying this (they

[jira] [Created] (SLING-5580) Resource Resolver Factory is wrongly activated when zero or more than one required providers

Carsten Ziegeler created SLING-5580: --- Summary: Resource Resolver Factory is wrongly activated when zero or more than one required providers Key: SLING-5580 URL: https://issues.apache.org/jira/browse/SLING-5580

[jira] [Assigned] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5579: --- Assignee: Carsten Ziegeler > setActive is not set to true during activation of >

[jira] [Updated] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5579: Fix Version/s: Resource Resolver 1.5.0 > setActive is not set to true during activation of

[jira] [Commented] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175599#comment-15175599 ] Santiago García Pimentel commented on SLING-5579: - a pull request:

[jira] [Commented] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175598#comment-15175598 ] Bertrand Delacretaz commented on SLING-5578: Building the commons/json module with {{mvn clean

[jira] [Updated] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

[ https://issues.apache.org/jira/browse/SLING-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santiago García Pimentel updated SLING-5579: Description: CommonResourceResolverFactoryImpl holds a bolean isActive

[jira] [Comment Edited] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175584#comment-15175584 ] Marius Petria edited comment on SLING-5578 at 3/2/16 1:29 PM: -- This can be

[jira] [Updated] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

[ https://issues.apache.org/jira/browse/SLING-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-5578: - Attachment: SLING-5578.diff This can be fixed by doing processing only at first level of

[GitHub] sling pull request: set isActive to true in the activate method

GitHub user santiagozky opened a pull request: https://github.com/apache/sling/pull/128 set isActive to true in the activate method You can merge this pull request into a Git repository by running: $ git pull https://github.com/santiagozky/sling SLING-5579 Alternatively you

[jira] [Created] (SLING-5579) setActive is not set to true during activation of CommonResourceResolverFactoryImpl

Santiago García Pimentel created SLING-5579: --- Summary: setActive is not set to true during activation of CommonResourceResolverFactoryImpl Key: SLING-5579 URL:

[jira] [Created] (SLING-5578) Json rendering is using recursion for processing flat trees and causes stack overflows

Marius Petria created SLING-5578: Summary: Json rendering is using recursion for processing flat trees and causes stack overflows Key: SLING-5578 URL: https://issues.apache.org/jira/browse/SLING-5578

[jira] [Resolved] (SLING-5559) Improve WebDAV support for installing a bundle

[ https://issues.apache.org/jira/browse/SLING-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-5559. Resolution: Fixed Fix Version/s: Maven Sling Plugin 2.1.8 Fixed in

[jira] [Updated] (SLING-5577) Distribution package implementation should be independent of serialization

[ https://issues.apache.org/jira/browse/SLING-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5577: --- Attachment: SLING-5577.0.patch attached first draft of {{ResourceDistributionPackage}}. The

[jira] [Created] (SLING-5577) Distribution package implementation should be independent of serialization

Tommaso Teofili created SLING-5577: -- Summary: Distribution package implementation should be independent of serialization Key: SLING-5577 URL: https://issues.apache.org/jira/browse/SLING-5577

[jira] [Created] (SLING-5576) Optimize queue items listing for big number of items by using iterators

Marius Petria created SLING-5576: Summary: Optimize queue items listing for big number of items by using iterators Key: SLING-5576 URL: https://issues.apache.org/jira/browse/SLING-5576 Project: Sling

Re: Random Failure to Deploy a File using AddOrUpdateNodeCommand

On Mon, 2016-02-29 at 16:02 -0800, Andreas Schaefer Sr. wrote: > Sorry for the late reply but I got bogged down by a customer going > live. > > Here is the stack trace: >  > Caused by: org.apache.sling.ide.transport.RepositoryException: > javax.jcr.ItemExistsException: Cannot add child node >

[RESULT][VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

On Tue, Feb 23, 2016 at 5:10 PM, Bertrand Delacretaz wrote: > ...Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1432/ ... The vote passes with 5 +1s and no other votes, thanks! I'll take care of the remaining steps. -Bertrand

Re: searchPath based on content path + multitenancy

Hi, On Tue, Mar 1, 2016 at 11:06 PM, Henry Saginor wrote: > ...Currently my application has a customized Servlet Resolver that does > this... If you're adventurous you could have a look at my content-based dynamic search path prototype at [1], that does something

Re: searchPath based on content path + multitenancy

Hi Henry, we had the same challenge, and instead of changing/patching the resource resolver we change the resource types. So each tenant has its own resourcetype namespace; for example /apps/tenannts/components/page/homepage. So we can use the "defaults" here, and just provide different

Re: [VOTE] Release Apache Sling Tooling Support Source 1.0.0

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: [VOTE] Release Apache Sling Tooling Support Source 1.0.0

+1 Cheers, Stefan On 01/03/16 16:22, "Robert Munteanu" wrote: >Hi, > >We solved 1 issues in this release: >https://issues.apache.org/jira/browse/SLING/fixforversion/12334884 > >Staging repository: >https://repository.apache.org/content/repositories/1436 > >You can use this