[jira] [Commented] (SLING-7429) Improve basename handling

[ https://issues.apache.org/jira/browse/SLING-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643699#comment-16643699 ] Alexander Klimetschek commented on SLING-7429: -- I would be very careful here risking any

Re: Removing loginAdministrative, how to test that, and service username conventions

Ok, I just noticed I replied to a super old thread because my Email app decided to surface it as if it were new :D Cheers, Alex > On 01.10.2018, at 16:19, Alexander Klimetschek > wrote: > > Hi Marius, > > AFAICS, what you describe below is exactly my @ServiceUse

Re: Removing loginAdministrative, how to test that, and service username conventions

Hi Marius, AFAICS, what you describe below is exactly my @ServiceUser annotation, just different names and a different syntax for the ACLs :) Cheers, Alex On 08.12.2015, at 08:09, Marius Petria wrote: > I do not have a precise use case right now other than obtaining a “content > access

Re: Limited search and find a file after git repo split

es I have used sourcegraph to search across repos like > https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/apache/sling-*++file:pom.xml. > It seems to pickup most of the repo matching given pattern > Chetan Mehrotra > > > On Wed, Jul 11, 2018 at 3:10 AM, Alexander Klim

Re: Limited search and find a file after git repo split

l Klco wrote: > >> I'm not sure we can do much about the old svn mirror being indexed, but >> adding a link to the Sling Aggregator sure would help. >> >> On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek >> wrote: >> >>> It seems nothing has r

Re: Limited search and find a file after git repo split

It seems nothing has really improved :) I just ended up on https://github.com/apache/sling-old-svn-mirror, trying to find sources from Sling, but really have no clue where it is, and the links on that readme don't help at all. Cheers, Alex > On 02.02.2018, at 19:12, Alexander Klimetsc

[jira] [Commented] (SLING-3524) ResourceResolver.clone(null) should not share the same JCR session

[ https://issues.apache.org/jira/browse/SLING-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460184#comment-16460184 ] Alexander Klimetschek commented on SLING-3524: -- Thanks, LGTM! Unit tests covering all paths

[jira] [Commented] (SLING-3524) ResourceResolver.clone(null) should not share the same JCR session

[ https://issues.apache.org/jira/browse/SLING-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458741#comment-16458741 ] Alexander Klimetschek commented on SLING-3524: -- [~Csaba Varga] I like it! Regarding the jcr

Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On 27.02.2018, at 22:07, Robert Munteanu wrote: > IIUC the proposal was to import the old svn mirror as a git repo, and > Betrand argued this would be a really large repo, and that's an > impediment for something which would be heavily cloned. You are right. It could be two

[jira] [Updated] (SLING-7510) UriProvider throws unchecked IllegalArgumentException that must be handled by consumers

[ https://issues.apache.org/jira/browse/SLING-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-7510: - Summary: UriProvider throws unchecked IllegalArgumentException that must

[jira] [Updated] (SLING-7510) UriProvider should throw a checked exception instead of IllegalArgumentException

[ https://issues.apache.org/jira/browse/SLING-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-7510: - Description: h3. Status quo A consumer of the [UriProvider|https://github.com

[jira] [Created] (SLING-7510) UriProvider should throw a checked exception instead of IllegalArgumentException

Alexander Klimetschek created SLING-7510: Summary: UriProvider should throw a checked exception instead of IllegalArgumentException Key: SLING-7510 URL: https://issues.apache.org/jira/browse/SLING-7510

Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On 12.02.2018, at 01:23, Robert Munteanu wrote: > The basic proposal as I see it would be to add a new 'sling' top-level > github repo, which means that: > > 1. we control what goes in there - README.md most importantly > 2. old links to sling commits and files will be broken

Re: apache/sling as github landing repository

ve a single git > repository that reflects all the other repositories? It would allow for a > central view, facilitate search, and still maintain a separation of the > individual projects. > > - Jason > > On Fri, Feb 2, 2018, at 10:16 PM, Alexander Klimetschek wrote: >> On 3

Re: apache/sling as github landing repository

On 31.01.2018, at 00:23, Robert Munteanu wrote: > Links to commits and files from the old sling repo. For example > > * https://github.com/apache/sling/commit/368f5f9c9f6d4c0e2602065687d95e > b173f94b85 > * https://github.com/apache/sling/blob/trunk/bundles/extensions/bundler

Re: Limited search and find a file after git repo split

On 30.01.2018, at 23:41, Robert Munteanu wrote: > After a quick look at the github pages my only suggestion is using the > advanced search page > > https://github.com/search/advanced > > and filling in all the sling repos in the repo field. The search would > then be

Limited search and find a file after git repo split

One thing that doesn't work well anymore after the repo split is a) quickly navigate to a file (hit key "T" in github) across all Sling code (e.g. if you know the api or have a stacktrace, but no idea what repo that is) b) search Unfortunately, github only indexes the main branch for b), so you

Re: apache/sling as github landing repository

On 30.01.2018, at 01:38, Robert Munteanu wrote: > The constraint that we worked with is that many links would be pointing > to https://github.com/apache/sling and these would be broken if we > added another 'sling' repository to the mix. So we decided to keep the > old

Re: apache/sling as github landing repository

On 29.01.2018, at 07:53, Bertrand Delacretaz wrote: > On Mon, Jan 29, 2018 at 4:08 PM, Daniel Klco wrote: >> ...I'd >> suspect that a majority of potential contributors would be coming through >> GitHub... > > Sure, and I agree to make sling/sling

apache/sling as github landing repository

Hi everyone, after the move to github and source code modularization (cool), the previous sling repository apache/sling [0] is now empty. Except for a readme that currently mostly addresses active committers (few, experts that know the context) rather than users of sling (many, newbies that

[jira] [Commented] (SLING-7300) CPU spike in i18n job

[ https://issues.apache.org/jira/browse/SLING-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286651#comment-16286651 ] Alexander Klimetschek commented on SLING-7300: -- All 3 dumps are inside the logging. Maybe

[jira] [Commented] (SLING-3049) Make Logback Stacktrace Packaging data support OSGi aware

[ https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225218#comment-16225218 ] Alexander Klimetschek commented on SLING-3049: -- +1 Looks very useful when people report

[jira] [Commented] (SLING-6935) Context-Aware web console default experience difficult

[ https://issues.apache.org/jira/browse/SLING-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177100#comment-16177100 ] Alexander Klimetschek commented on SLING-6935: -- Thanks! > Context-Aware web console defa

[jira] [Commented] (SLING-7014) Inheritance of configurations from parent content resource

[ https://issues.apache.org/jira/browse/SLING-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090251#comment-16090251 ] Alexander Klimetschek commented on SLING-7014: -- [~cziegeler] [~sseif...@pro-vision.de] Could

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041485#comment-16041485 ] Alexander Klimetschek edited comment on SLING-848 at 6/7/17 7:34 PM

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041485#comment-16041485 ] Alexander Klimetschek edited comment on SLING-848 at 6/7/17 7:34 PM

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16041485#comment-16041485 ] Alexander Klimetschek commented on SLING-848: - [~cziegeler] {quote}Looking at the quoted

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:53 PM

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:52 PM

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:52 PM

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek commented on SLING-848: - The original filename that triggered this issue

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037662#comment-16037662 ] Alexander Klimetschek edited comment on SLING-848 at 6/5/17 9:56 PM

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037662#comment-16037662 ] Alexander Klimetschek edited comment on SLING-848 at 6/5/17 9:51 PM

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037662#comment-16037662 ] Alexander Klimetschek commented on SLING-848: - [~tomek.rekawek] [~cziegeler] This change looks

[jira] [Commented] (SLING-6935) Context-Aware web console default experience difficult

[ https://issues.apache.org/jira/browse/SLING-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035391#comment-16035391 ] Alexander Klimetschek commented on SLING-6935: -- BTW, instead of a service user it could use

[jira] [Created] (SLING-6935) Context-Aware web console default experience difficult

Alexander Klimetschek created SLING-6935: Summary: Context-Aware web console default experience difficult Key: SLING-6935 URL: https://issues.apache.org/jira/browse/SLING-6935 Project: Sling

[jira] [Updated] (SLING-6932) [javadoc] Document transient nature of ResourceResolver operations

[ https://issues.apache.org/jira/browse/SLING-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6932: - Description: All ResourceResolver resource operations (create, delete, move, copy

Re: [API] ResourceResolver.copy/move() transient or not?

ache.org/apidocs/sling8/org/apache/sling/api/resource/ResourceResolver.html >> [4] >> https://github.com/apache/sling/commit/6653209154a464f45fa63634af869408d6b84619 >> >> Cheers, >> Alex >> >>> On 31.05.2017, at 17:34, Alexander Klimetschek <aklim...@adobe.c

[jira] [Created] (SLING-6932) [javadoc] Document transient nature of ResourceResolver operations

Alexander Klimetschek created SLING-6932: Summary: [javadoc] Document transient nature of ResourceResolver operations Key: SLING-6932 URL: https://issues.apache.org/jira/browse/SLING-6932

Re: [API] ResourceResolver.copy/move() transient or not?

/6653209154a464f45fa63634af869408d6b84619 Cheers, Alex > On 31.05.2017, at 17:34, Alexander Klimetschek <aklim...@adobe.com.INVALID> > wrote: > > Hi everyone, > > the javadocs of ResourceResolver.copy/move() [1] aren't very clear whether > these methods imm

[API] ResourceResolver.copy/move() transient or not?

Hi everyone, the javadocs of ResourceResolver.copy/move() [1] aren't very clear whether these methods immediately persist the change, or if the change is transient and it's necessary to call commit(). The implementation of the JCR resource provider uses Session.move() which is transient.

[jira] [Commented] (SLING-6890) Remove usage of o.a.jackrabbit.commons.json from i18n

[ https://issues.apache.org/jira/browse/SLING-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030046#comment-16030046 ] Alexander Klimetschek commented on SLING-6890: -- Where did you saw it? The code itself has

[jira] [Commented] (SLING-6826) i18n: Supported nested keys in JSON i18n files

[ https://issues.apache.org/jira/browse/SLING-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998790#comment-15998790 ] Alexander Klimetschek commented on SLING-6826: -- {quote}this "((comment))" con

[jira] [Commented] (SLING-6826) i18n: Supported nested keys in JSON i18n files

[ https://issues.apache.org/jira/browse/SLING-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997693#comment-15997693 ] Alexander Klimetschek commented on SLING-6826: -- This means the nested structure maps

[jira] [Commented] (SLING-6826) i18n: Supported nested keys in JSON i18n files

[ https://issues.apache.org/jira/browse/SLING-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995856#comment-15995856 ] Alexander Klimetschek commented on SLING-6826: -- What is the use case for supporting nested

[jira] [Comment Edited] (SLING-6777) ValidationServiceImpl breaks when hitting closed resolver for resource bundles (i18n)

[ https://issues.apache.org/jira/browse/SLING-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965637#comment-15965637 ] Alexander Klimetschek edited comment on SLING-6777 at 4/12/17 10:06 AM

[jira] [Commented] (SLING-6777) ValidationServiceImpl breaks when hitting closed resolver for resource bundles (i18n)

[ https://issues.apache.org/jira/browse/SLING-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965637#comment-15965637 ] Alexander Klimetschek commented on SLING-6777: -- At first, I can only see this happening

[jira] [Commented] (SLING-6719) Add Server-Timing header to enable chrome log server timings

[ https://issues.apache.org/jira/browse/SLING-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943521#comment-15943521 ] Alexander Klimetschek commented on SLING-6719: -- The request progress tracker log could

[jira] [Commented] (SLING-6552) ResourceResolver must be independent from javax.jcr

[ https://issues.apache.org/jira/browse/SLING-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892684#comment-15892684 ] Alexander Klimetschek commented on SLING-6552: -- Does this actually work if no javax.jcr

[jira] [Comment Edited] (SLING-6552) ResourceResolver must be independent from javax.jcr

[ https://issues.apache.org/jira/browse/SLING-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892684#comment-15892684 ] Alexander Klimetschek edited comment on SLING-6552 at 3/2/17 5:51 PM

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826747#comment-15826747 ] Alexander Klimetschek commented on SLING-6187: -- Ah, thanks for the test. This wasn't apparent

[jira] [Comment Edited] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826728#comment-15826728 ] Alexander Klimetschek edited comment on SLING-6187 at 1/17/17 8:13 PM

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826728#comment-15826728 ] Alexander Klimetschek commented on SLING-6187: -- Thanks [~justinedelson]. AFAICS, the patch

[jira] [Comment Edited] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826728#comment-15826728 ] Alexander Klimetschek edited comment on SLING-6187 at 1/17/17 8:14 PM

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760252#comment-15760252 ] Alexander Klimetschek commented on SLING-6187: -- It wouldn't be prohibited in general

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752215#comment-15752215 ] Alexander Klimetschek commented on SLING-6187: -- IIUC, the new validating patch requires

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748802#comment-15748802 ] Alexander Klimetschek commented on SLING-6187: -- The core of the issue is that the use

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746895#comment-15746895 ] Alexander Klimetschek commented on SLING-6187: -- The point is _additional_ parameter

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746876#comment-15746876 ] Alexander Klimetschek commented on SLING-6187: -- FWIW: All approaches require changes

[jira] [Comment Edited] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746852#comment-15746852 ] Alexander Klimetschek edited comment on SLING-6187 at 12/14/16 1:26 AM

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746852#comment-15746852 ] Alexander Klimetschek commented on SLING-6187: -- My view now is that a post processor

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15746788#comment-15746788 ] Alexander Klimetschek commented on SLING-6187: -- What about this alternative

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15745678#comment-15745678 ] Alexander Klimetschek commented on SLING-6187: -- [~fmeschbe] The problem is if you have

[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those

[ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732716#comment-15732716 ] Alexander Klimetschek commented on SLING-5745: -- Unfortunately we could not find any hint

[jira] [Comment Edited] (SLING-5745) Provide a button to clear all registered entities and reinstall those

[ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730412#comment-15730412 ] Alexander Klimetschek edited comment on SLING-5745 at 12/8/16 12:24 AM

[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those

[ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15730412#comment-15730412 ] Alexander Klimetschek commented on SLING-5745: -- +1 We just had such a situation and doing

Build test failures

I have some trouble building Sling (all of it, it's been a while since I tried that :) 1. It seems the Sling build requires Java 1.8 ("Apache Sling Testing PaxExam" project failed with not all bundles loaded when I ran it with a 1.7 JDK). A check/hint at the start of the build would be great.

[jira] [Comment Edited] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613238#comment-15613238 ] Alexander Klimetschek edited comment on SLING-6187 at 10/27/16 9:17 PM

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15613238#comment-15613238 ] Alexander Klimetschek commented on SLING-6187: -- Could this check be based on the resource

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606603#comment-15606603 ] Alexander Klimetschek commented on SLING-6187: -- regarding 2): the @suffix is in a separate

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

[ https://issues.apache.org/jira/browse/SLING-6187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15606487#comment-15606487 ] Alexander Klimetschek commented on SLING-6187: -- Having clients to specify that doesn't feel

[jira] [Commented] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies

[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605824#comment-15605824 ] Alexander Klimetschek commented on SLING-6165: -- SLING-5277 has a [patch|https

[jira] [Comment Edited] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605790#comment-15605790 ] Alexander Klimetschek edited comment on SLING-5277 at 10/25/16 4:39 PM

[jira] [Commented] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies

[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605795#comment-15605795 ] Alexander Klimetschek commented on SLING-6165: -- Would be great

[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605790#comment-15605790 ] Alexander Klimetschek commented on SLING-5277: -- AFAICS, SLING-6165 just moves

[jira] [Comment Edited] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603702#comment-15603702 ] Alexander Klimetschek edited comment on SLING-5277 at 10/25/16 12:53 AM

[jira] [Updated] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-5277: - Attachment: SLING-5277-new.patch Attached new patch [^SLING-5277-new.patch] which

[jira] [Updated] (SLING-6180) Show slowest filters sorted by total time in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Summary: Show slowest filters sorted by total time in filter status webconsole

[jira] [Comment Edited] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15597291#comment-15597291 ] Alexander Klimetschek edited comment on SLING-6180 at 10/22/16 6:50 AM

[jira] [Updated] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Attachment: (was: SLING-6180.patch) > Show slowest filters sorted by time

[jira] [Updated] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Attachment: SLING-6180.patch > Show slowest filters sorted by time per requ

[jira] [Updated] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Attachment: SLING-6180.patch Attaching a new version that fixes a memory leak

[jira] [Updated] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Attachment: (was: SLING-6180.patch) > Show slowest filters sorted by time

[jira] [Comment Edited] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15596897#comment-15596897 ] Alexander Klimetschek edited comment on SLING-6180 at 10/22/16 1:34 AM

[jira] [Updated] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

[ https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-6180: - Attachment: SLING-6180.patch Attached a patch: [^SLING-6180.patch

[jira] [Created] (SLING-6180) Show slowest filters sorted by time per request in filter status webconsole

Alexander Klimetschek created SLING-6180: Summary: Show slowest filters sorted by time per request in filter status webconsole Key: SLING-6180 URL: https://issues.apache.org/jira/browse/SLING-6180

[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings

[ https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-4558: - Issue Type: Improvement (was: Bug) > Simpler serviceuser config for service u

[jira] [Comment Edited] (SLING-5274) Include authentication in RequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145701#comment-15145701 ] Alexander Klimetschek edited comment on SLING-5274 at 2/13/16 1:55 AM

[jira] [Comment Edited] (SLING-5274) Include authentication in RequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145701#comment-15145701 ] Alexander Klimetschek edited comment on SLING-5274 at 2/13/16 1:55 AM

[jira] [Commented] (SLING-5274) Include authentication in RequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145701#comment-15145701 ] Alexander Klimetschek commented on SLING-5274: -- Thanks Bertrand for SLING-5489, it's a good

[jira] [Updated] (SLING-5448) AuthenticationInfoPostProcessor javadoc misleading

[ https://issues.apache.org/jira/browse/SLING-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-5448: - Description: Currently, the [AuthenticationInfoPostProcessor javadoc says|https

[jira] [Created] (SLING-5448) AuthenticationInfoPostProcessor javadoc misleading

Alexander Klimetschek created SLING-5448: Summary: AuthenticationInfoPostProcessor javadoc misleading Key: SLING-5448 URL: https://issues.apache.org/jira/browse/SLING-5448 Project: Sling

[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081843#comment-15081843 ] Alexander Klimetschek commented on SLING-5277: -- To fix the DESTROY handling, we can just call

[jira] [Comment Edited] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081834#comment-15081834 ] Alexander Klimetschek edited comment on SLING-5277 at 1/4/16 9:24 PM

[jira] [Comment Edited] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081834#comment-15081834 ] Alexander Klimetschek edited comment on SLING-5277 at 1/4/16 9:25 PM

[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081834#comment-15081834 ] Alexander Klimetschek commented on SLING-5277: -- Good catch. It doesn't need to be created

[jira] [Commented] (SLING-5277) Performance: per thread script resolver (admin session) is always created even if cache is hit

[ https://issues.apache.org/jira/browse/SLING-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006105#comment-15006105 ] Alexander Klimetschek commented on SLING-5277: -- The patch does exactly that. In my

[jira] [Commented] (SLING-5288) Restrict which classes can be deserialized

[ https://issues.apache.org/jira/browse/SLING-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998939#comment-14998939 ] Alexander Klimetschek commented on SLING-5288: -- For performance reasons I would use a hash

[jira] [Commented] (SLING-4937) Drop namespace mapping support

[ https://issues.apache.org/jira/browse/SLING-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14997921#comment-14997921 ] Alexander Klimetschek commented on SLING-4937: -- It also helps with performance A LOT

[jira] [Updated] (SLING-5274) Include authentication in RequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-5274: - Flags: Patch > Include authentication in RequestProgressTrac

  1   2   3   4   5   6   7   8   >