[jira] [Commented] (SLING-6963) Service user declaration based on principal names

[ https://issues.apache.org/jira/browse/SLING-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050578#comment-16050578 ] Felix Meschberger commented on SLING-6963: -- Thanks, [~anchela]. I quickly reviewed the patch

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

[ https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953564#comment-15953564 ] Felix Meschberger commented on SLING-6702: -- bq. prevent it from getting unregistering [~chetanm

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

[ https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939032#comment-15939032 ] Felix Meschberger commented on SLING-6702: -- I appreciate the idea and I agree it makes a lot

[jira] [Commented] (SLING-6609) Fix JSR305 annotations for ValueMap.get

[ https://issues.apache.org/jira/browse/SLING-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897939#comment-15897939 ] Felix Meschberger commented on SLING-6609: -- Thanks, [~kwin]. Looks good except, I'd defer

[jira] [Commented] (SLING-6609) Fix JSR305 annotations for ValueMap.get

[ https://issues.apache.org/jira/browse/SLING-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897208#comment-15897208 ] Felix Meschberger commented on SLING-6609: -- Fully agreed with the safety net for compile time

[jira] [Commented] (SLING-6609) Fix JSR305 annotations for ValueMap.get

[ https://issues.apache.org/jira/browse/SLING-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897056#comment-15897056 ] Felix Meschberger commented on SLING-6609: -- Ah, right, but historically, I am not sure

[jira] [Commented] (SLING-6609) Fix JSR305 annotations for ValueMap.get

[ https://issues.apache.org/jira/browse/SLING-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896981#comment-15896981 ] Felix Meschberger commented on SLING-6609: -- Actually, I am not entirely sure, whether @Nonnull

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890132#comment-15890132 ] Felix Meschberger commented on SLING-6578: -- bq. Now coming to the point of overloading

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890105#comment-15890105 ] Felix Meschberger commented on SLING-6578: -- Hmm, in a private conversation [~cziegeler] mentioned

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890027#comment-15890027 ] Felix Meschberger commented on SLING-6578: -- I don't understand this ? Is the general use

[jira] [Comment Edited] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890012#comment-15890012 ] Felix Meschberger edited comment on SLING-6578 at 3/1/17 11:37 AM: --- bq

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890012#comment-15890012 ] Felix Meschberger commented on SLING-6578: -- bq. service.pid is not reliable - with a DS component

[jira] [Comment Edited] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889983#comment-15889983 ] Felix Meschberger edited comment on SLING-6578 at 3/1/17 11:09 AM: --- I

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889983#comment-15889983 ] Felix Meschberger commented on SLING-6578: -- I like [~olli] idea. The property is easily

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889982#comment-15889982 ] Felix Meschberger commented on SLING-6578: -- TL;DR: Suggest to still use the service.pid. Define

[jira] [Comment Edited] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889802#comment-15889802 ] Felix Meschberger edited comment on SLING-6578 at 3/1/17 11:04 AM: --- I

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889818#comment-15889818 ] Felix Meschberger commented on SLING-6578: -- Beware, though, [~kwin]: "component.name&quo

[jira] [Comment Edited] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889802#comment-15889802 ] Felix Meschberger edited comment on SLING-6578 at 3/1/17 9:03 AM: -- I

[jira] [Commented] (SLING-6578) Use "service.pid" property instead of class name to reference validators

[ https://issues.apache.org/jira/browse/SLING-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889802#comment-15889802 ] Felix Meschberger commented on SLING-6578: -- I think we should still use the service.pid

Re: SLING_ prefix for selectors that we use "internally" ?

Hi But if you insiste on a prefix, I suggest to use something nicer looking than SLING_. How about sling. ? Hence sling.bla such as /path/to/resource.sling.bla.html ? Yet, I agree with Carsten that I am not sure, whether this really is required. On the other hand, using a specific selector

[jira] [Comment Edited] (SLING-6548) Provide framework extension fragment for Servlet JSP API

[ https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878370#comment-15878370 ] Felix Meschberger edited comment on SLING-6548 at 2/22/17 2:58 PM: --- I am

[jira] [Commented] (SLING-6549) Provide framework extension fragment for EL API

[ https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878384#comment-15878384 ] Felix Meschberger commented on SLING-6549: -- [~olli] Thanks for the reference, just commented

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878380#comment-15878380 ] Felix Meschberger commented on SLING-6502: -- Hmm, I think the things you are doing here

[jira] [Comment Edited] (SLING-6549) Provide framework extension fragment for EL API

[ https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878367#comment-15878367 ] Felix Meschberger edited comment on SLING-6549 at 2/22/17 2:54 PM: --- I am

[jira] [Commented] (SLING-6548) Provide framework extension fragment for Servlet JSP API

[ https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878370#comment-15878370 ] Felix Meschberger commented on SLING-6548: -- I am not sure, this is a good idea ! JSP API must

[jira] [Commented] (SLING-6549) Provide framework extension fragment for EL API

[ https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878367#comment-15878367 ] Felix Meschberger commented on SLING-6549: -- I am not sure, this is a good idea ! EL must

[jira] [Comment Edited] (SLING-6550) Remove Servlet API from org.apache.sling.launcher.system.packages

[ https://issues.apache.org/jira/browse/SLING-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878344#comment-15878344 ] Felix Meschberger edited comment on SLING-6550 at 2/22/17 2:45 PM: --- Can

[jira] [Commented] (SLING-6550) Remove Servlet API from org.apache.sling.launcher.system.packages

[ https://issues.apache.org/jira/browse/SLING-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878344#comment-15878344 ] Felix Meschberger commented on SLING-6550: -- Can you elaborate a bit what this is about

[jira] [Commented] (SLING-6046) While Streaming Video to IE 11, StreamRendererServlet do not use Partial Content Response [code 206]

[ https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864731#comment-15864731 ] Felix Meschberger commented on SLING-6046: -- > The patch we finally applied actually sends Ra

Re: Exclude IntelliJ Modules Files from rat plugin

Hi Goot point. And also: Are these files in subversion ? If they are, they should be removed and excluded by configuration. They don’t belong there. Regards Felix > Am 27.01.2017 um 11:24 schrieb Clelia Meneghin : > > Hi > > Currently any present IntelliJ Module Files

Re: Name conventions for our core metrics?

Hi I like hierarchical names for name spacing. But can we do as most people do today and just use dots (thus remove the colon) ? Not sure whether we should stiplute a relation to the bundle or package name they are defined in because that might have negative consequences in case of

[jira] [Commented] (SLING-6458) JSP scripting does not support Java 8 features (lambdas, method references, etc)

[ https://issues.apache.org/jira/browse/SLING-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821692#comment-15821692 ] Felix Meschberger commented on SLING-6458: -- Thanks [~cziegeler]. In this case I stand corrected

[jira] [Commented] (SLING-6458) JSP scripting does not support Java 8 features (lambdas, method references, etc)

[ https://issues.apache.org/jira/browse/SLING-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821647#comment-15821647 ] Felix Meschberger commented on SLING-6458: -- There are two topics here: * First that we are based

[jira] [Commented] (SLING-6046) While Streaming Video to IE 11, StreamRendererServlet do not use Partial Content Response [code 206]

[ https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803983#comment-15803983 ] Felix Meschberger commented on SLING-6046: -- Proposing following patch with a threshold size

[jira] [Resolved] (SLING-6433) Request Processing Analyzer throws IOOB due to old format assumptions of RequestProgressTracker output

[ https://issues.apache.org/jira/browse/SLING-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-6433. -- Resolution: Fixed Assignee: Felix Meschberger Thanks for providing the patch. I

[jira] [Commented] (SLING-4753) Commit the Resource Resolver before passing it to Tenant Customizers for setting up their own customizations

[ https://issues.apache.org/jira/browse/SLING-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769793#comment-15769793 ] Felix Meschberger commented on SLING-4753: -- Thanks [~marett]. Looking at the support for the post

[jira] [Comment Edited] (SLING-4753) Commit the Resource Resolver before passing it to Tenant Customizers for setting up their own customizations

[ https://issues.apache.org/jira/browse/SLING-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769366#comment-15769366 ] Felix Meschberger edited comment on SLING-4753 at 12/22/16 7:37 AM

[jira] [Reopened] (SLING-4753) Commit the Resource Resolver before passing it to Tenant Customizers for setting up their own customizations

[ https://issues.apache.org/jira/browse/SLING-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-4753: -- Reopening as I think this is not done yet. > Commit the Resource Resolver before pass

[jira] [Commented] (SLING-4753) Commit the Resource Resolver before passing it to Tenant Customizers for setting up their own customizations

[ https://issues.apache.org/jira/browse/SLING-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769366#comment-15769366 ] Felix Meschberger commented on SLING-4753: -- Hmm, I am a bit concerned, yet, of course, late

Re: [api] type conversion in ValueMapDecorator

Hi Granted, consolidation probably makes sense, but there are caveats: * Bloat: Please consider to not bloat the conversion functionality and carefully consider which conversion really makes sense and which is just nice-to-have-because-JCR-has-it. * API: I suggest to break this out of the

Re: VanityPath and ResourceResolver#map

Hi > Am 16.12.2016 um 13:22 schrieb Carsten Ziegeler : > > Justin Edelson wrote >> Hi, >> IIUC, this is by design. Vanity paths are intended for inbound use only. >> > > Right, they might not be as "stable" as a mapping, e.g /latestnews might > point to page A now, but to

[jira] [Commented] (SLING-6352) do not use unstable Jackrabbit releases

[ https://issues.apache.org/jira/browse/SLING-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15751551#comment-15751551 ] Felix Meschberger commented on SLING-6352: -- To be honest, I don't exactly remember why we chose

Re: [slingstart] Overriding a variable from the command line at runtime

Hi I think this is a good topic to discuss on a broader level. I once implemented a function with two services configured through OSGi Configuration being able to overwritten by framework properties (aka system properties). What I did implement is a helper function which first checked the

Re: [slingstart] Overriding a variable from the command line at runtime

Am 14.12.2016 um 15:38 schrieb Carsten Ziegeler <cziege...@apache.org<mailto:cziege...@apache.org>>: Felix Meschberger wrote Hi I think this is a good topic to discuss on a broader level. I once implemented a function with two services configured through OSGi Configuratio

Re: Provide a way for a POST request to assert a set of required SlingPostProcessors (SLING-6187)

Hi Justin Thanks for the clarification Am 14.12.2016 um 15:14 schrieb Justin Edelson <jus...@justinedelson.com<mailto:jus...@justinedelson.com>>: Hi Felix, On Wed, Dec 14, 2016 at 8:46 AM Felix Meschberger <fmesc...@adobe.com<mailto:fmesc...@adobe.com>> wro

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

read the proposed > implementation). What problem does this solution try to solve ? Justin replied: > Felix Meschberger the use case is laid out in the issue description – a POST > request may depend upon the presence of one or more post processors. Actually, the issue description essentially just

[jira] [Commented] (SLING-6394) SlingAuthenticatior#getAnonymousResolver doesn't take in consideration vanityPath

[ https://issues.apache.org/jira/browse/SLING-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15745616#comment-15745616 ] Felix Meschberger commented on SLING-6394: -- Yes, that's correct because the Sling Authenticator

[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=15745591#comment-15745591 ] Felix Meschberger commented on SLING-6187: -- [~justinedelson] I share [~alexander.klimetschek]'s

[jira] [Resolved] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-6378. -- Resolution: Fixed Fixed in Rev. 1773793: * Converted the SlingDavExServlet

[jira] [Commented] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741518#comment-15741518 ] Felix Meschberger commented on SLING-6378: -- Thanks for the feedback. I am going for Option (2

[jira] [Assigned] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-6378: Assignee: Felix Meschberger > Unclosed ResourceResolver in davex AuthHttpCont

[jira] [Updated] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-6378: - Fix Version/s: JCR Davex 1.3.6 > Unclosed ResourceResolver in davex AuthHttpCont

[jira] [Commented] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735746#comment-15735746 ] Felix Meschberger commented on SLING-6378: -- The problem is that the traditional {{HttpService

[jira] [Comment Edited] (SLING-6383) Unexpected behavior with left curly bracket in resource resolution

[ https://issues.apache.org/jira/browse/SLING-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735427#comment-15735427 ] Felix Meschberger edited comment on SLING-6383 at 12/9/16 2:14 PM

[jira] [Comment Edited] (SLING-6383) Unexpected behavior with left curly bracket in resource resolution

[ https://issues.apache.org/jira/browse/SLING-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735427#comment-15735427 ] Felix Meschberger edited comment on SLING-6383 at 12/9/16 2:14 PM

[jira] [Commented] (SLING-6383) Unexpected behavior with left curly bracket in resource resolution

[ https://issues.apache.org/jira/browse/SLING-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735427#comment-15735427 ] Felix Meschberger commented on SLING-6383: -- Could this be that JCR assumes the leading curly

[jira] [Commented] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732424#comment-15732424 ] Felix Meschberger commented on SLING-6378: -- I quickly looked into the code. The only hint I would

[jira] [Commented] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732376#comment-15732376 ] Felix Meschberger commented on SLING-6378: -- SlingAuthenticator is a service which is referenced

[jira] [Commented] (SLING-6378) Unclosed ResourceResolver in davex AuthHttpContext

[ https://issues.apache.org/jira/browse/SLING-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732293#comment-15732293 ] Felix Meschberger commented on SLING-6378: -- What version of the Sling Authentication Core bundle

[jira] [Commented] (SLING-6046) While Streaming Video to IE 11, StreamRendererServlet do not use Partial Content Response [code 206]

[ https://issues.apache.org/jira/browse/SLING-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732181#comment-15732181 ] Felix Meschberger commented on SLING-6046: -- I think we should not apply the patch

[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=15731513#comment-15731513 ] Felix Meschberger commented on SLING-5745: -- Nice workaround, but ... Why is the state corrupt

Re: New JSON library

Hi I like this approach. As to replacement options: I'd go for Apache Johnzon. First it's Apache hence eating our own dogfood. But more importantly, it is an implementation of the standard javax.json API. I much prefer standard APIs over the fragmented JSON API scene. Regards Felix Von

[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=15701663#comment-15701663 ] Felix Meschberger commented on SLING-6165: -- Note, that Sling indeed does not do

Re: How to handle minor version updates in API for provider bundles?

/browse/SLING-6327 for further details. Ok, technically it looks like it is breaking. But I have the impression, this makes sense and is more consistent with RR.getResource. Thanks Felix > Konrad > >> On 28 Nov 2016, at 09:42, Felix Meschberger <fmesc...@adobe.com> wrote: >>

Re: How to handle minor version updates in API for provider bundles?

Hi Konrad Hmm, are these changed semantics backwards compatible ? I.e. what do existing callers have to expect ? Regards Felix > Am 26.11.2016 um 17:18 schrieb Konrad Windszus : > > Moving the Util methods somewhere else (and even making that Util private) is > fine with me,

[jira] [Commented] (SLING-6328) JSP concurrent compiling issue

[ https://issues.apache.org/jira/browse/SLING-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695278#comment-15695278 ] Felix Meschberger commented on SLING-6328: -- [~rombert] According to the bug referenced

[jira] [Commented] (SLING-6315) o.a.sling.scripting.core: IllegalStateException: The bundle is uninstalled

[ https://issues.apache.org/jira/browse/SLING-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689557#comment-15689557 ] Felix Meschberger commented on SLING-6315: -- bq. Is it still possible to have a race condition

[jira] [Commented] (SLING-6315) o.a.sling.scripting.core: IllegalStateException: The bundle is uninstalled

[ https://issues.apache.org/jira/browse/SLING-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689529#comment-15689529 ] Felix Meschberger commented on SLING-6315: -- Rather than try-catching (on every event even !) I

Re: Ensuring that components have a configuration when started

Hi I suggest to attack the problem at the right place ! When Configuration Admin is active and configuration is stored in Configuration Admin, then configuration *is* provided as soon as such components are activated. If not, this is an SCR bug. Now, I assume you have a provisioning problem

[jira] [Commented] (SLING-6258) The PackageAdminClassLoader cannot load classes from bundles providing older API versions

[ https://issues.apache.org/jira/browse/SLING-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654207#comment-15654207 ] Felix Meschberger commented on SLING-6258: -- [~radu.cotescu] From what I can tell, this looks good

Re: [Documentation] Sling Job documentation uses immediate component

Hi Justin EventAdmin will getService and ungetService the matching EventHandler services for each event to be dispatched. If the component is a delayed service, which as you state is the default, this means the instance is created and dropped for every single event. If there are a lot of them,

Re: [jira] [Resolved] (SLING-6258) The PackageAdminClassLoader cannot load classes from bundles providing older API versions

Hi Radu Not currently able to log into JIRA. This fix wrong and fails on you. First the OSGi spec says to resolve to the highest matching version of a package and not just any. So our PackageAdminClassLoader should do the same. Even ignoring this, you must make sure to always use the same

[jira] [Resolved] (SLING-6253) Make it easier to have single bundle projects

[ https://issues.apache.org/jira/browse/SLING-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-6253. -- Resolution: Fixed Fix Version/s: (was: Slingstart Maven Plugin 1.5.0) Only

[jira] [Assigned] (SLING-6253) Make it easier to have single bundle projects

[ https://issues.apache.org/jira/browse/SLING-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-6253: Assignee: Felix Meschberger > Make it easier to have single bundle proje

[jira] [Closed] (SLING-6253) Make it easier to have single bundle projects

[ https://issues.apache.org/jira/browse/SLING-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-6253. > Make it easier to have single bundle proje

[jira] [Created] (SLING-6253) Make it easier to have single bundle projects

Felix Meschberger created SLING-6253: Summary: Make it easier to have single bundle projects Key: SLING-6253 URL: https://issues.apache.org/jira/browse/SLING-6253 Project: Sling Issue

[jira] [Resolved] (SLING-6226) substVars not properly handling unknown properties

[ https://issues.apache.org/jira/browse/SLING-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-6226. -- Resolution: Fixed Thanks [~cziegeler]. Committed the patch in Rev. 1767618

[jira] [Assigned] (SLING-6226) substVars not properly handling unknown properties

[ https://issues.apache.org/jira/browse/SLING-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-6226: Assignee: Felix Meschberger > substVars not properly handling unknown propert

Re: [jira] [Created] (SLING-6226) substVars not properly handling unknown properties

Hi all I think this works as in „works on my machine“. Can I have someone please review this patch ? Thanks Felix > Am 01.11.2016 um 16:54 schrieb Felix Meschberger (JIRA) <j...@apache.org>: > > Felix Meschberger cre

[jira] [Updated] (SLING-6226) substVars not properly handling unknown properties

[ https://issues.apache.org/jira/browse/SLING-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-6226: - Attachment: SLING-6226.diff Proposed patch adding the Util class, removing the old

[jira] [Updated] (SLING-6226) substVars not properly handling unknown properties

[ https://issues.apache.org/jira/browse/SLING-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-6226: - Flags: Patch > substVars not properly handling unknown propert

[jira] [Created] (SLING-6226) substVars not properly handling unknown properties

Felix Meschberger created SLING-6226: Summary: substVars not properly handling unknown properties Key: SLING-6226 URL: https://issues.apache.org/jira/browse/SLING-6226 Project: Sling

[jira] [Commented] (SLING-6222) [Startup ERROR] org.apache.sling.commons.mime FrameworkEvent ERROR (The bundle is uninstalled.)

[ https://issues.apache.org/jira/browse/SLING-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625609#comment-15625609 ] Felix Meschberger commented on SLING-6222: -- Looks like a concurrency situation with bundles

Re: Logback setup

Hi Chetan Here you go: https://issues.apache.org/jira/browse/SLING-6220 Please review. Works in my environment, but … ;-) Thanks Felix Am 01.11.2016 um 05:59 schrieb Chetan Mehrotra <chetan.mehro...@gmail.com<mailto:chetan.mehro...@gmail.com>>: On Fri, Oct 28, 2016 at 9:

[jira] [Created] (SLING-6220) [log] Perform initial configuration from framework properties synchronously

Felix Meschberger created SLING-6220: Summary: [log] Perform initial configuration from framework properties synchronously Key: SLING-6220 URL: https://issues.apache.org/jira/browse/SLING-6220

Logback setup

Hi all I just noted a problem in the way the logging infrastructure is configured currently with Sling Commons Log 5.0. I have a use case, where I have the global configuration provided as properties in sling.properties. This configuration is log file name, log format pattern, and log file

Re: [JSON] Replacing json.org

, but create awareness. Regards Felix > Am 28.10.2016 um 12:57 schrieb Robert Munteanu <romb...@apache.org>: > > On Fri, 2016-10-28 at 08:08 +, Felix Meschberger wrote: >> Hi all >> >> Over at legal-discuss there is a discussion of whether the json.org >&g

[JSON] Replacing json.org

Hi all Over at legal-discuss there is a discussion of whether the json.org library with the amended MIT license (remember the „use for good not evil“ clause ?) should be „banned“ by reconsidering the „A“ rating of this license (assuming the clause is just a joke) and turning it into an „X“

[jira] [Commented] (SLING-5866) DefaultGetServlet obtains input stream for binary even if request is a HEAD

[ https://issues.apache.org/jira/browse/SLING-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384221#comment-15384221 ] Felix Meschberger commented on SLING-5866: -- The most important uses IIRC for a HEAD request

[jira] [Commented] (SLING-5414) Make the contents of the provisioning model available at runtime

[ https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15129982#comment-15129982 ] Felix Meschberger commented on SLING-5414: -- >From the peanut gallery: Providing the model is

[jira] [Commented] (SLING-5035) Sling Models Injectors should be queried in the reverse order of their service ranking value

[ https://issues.apache.org/jira/browse/SLING-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803164#comment-14803164 ] Felix Meschberger commented on SLING-5035: -- Quoting the OSGi Core Specification R6 : {panel

[jira] [Commented] (SLING-4717) Option to indent output in request progress tracker log

[ https://issues.apache.org/jira/browse/SLING-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549941#comment-14549941 ] Felix Meschberger commented on SLING-4717: -- Ok, its yet another configuration

[jira] [Commented] (SLING-4717) Option to indent output in request progress tracker log

[ https://issues.apache.org/jira/browse/SLING-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14547593#comment-14547593 ] Felix Meschberger commented on SLING-4717: -- Sounds interesting at first sight

[jira] [Updated] (SLING-4656) ProviderHandler implements compareTo incorreclty

[ https://issues.apache.org/jira/browse/SLING-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4656: - Description: The implementation of the ResourceResolver's compareTo method is wrong

[jira] [Commented] (SLING-4656) ProviderHandler implements compareTo incorreclty

[ https://issues.apache.org/jira/browse/SLING-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510660#comment-14510660 ] Felix Meschberger commented on SLING-4656: -- Thanks for the tests. Will fix

[jira] [Assigned] (SLING-4656) ProviderHandler implements compareTo incorreclty

[ https://issues.apache.org/jira/browse/SLING-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4656: Assignee: Felix Meschberger ProviderHandler implements compareTo incorreclty

[jira] [Resolved] (SLING-4655) Servlet Resolver does not use registered servlet's service.ranking property

[ https://issues.apache.org/jira/browse/SLING-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4655. -- Resolution: Fixed Assignee: Felix Meschberger Fixed in Rev. 1675803: * Added

[jira] [Resolved] (SLING-4656) ProviderHandler implements compareTo incorreclty

[ https://issues.apache.org/jira/browse/SLING-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4656. -- Resolution: Fixed Fixed in Rev. 1675805: * Document natural order of ProviderHandler

[jira] [Comment Edited] (SLING-4655) Servlet Resolver does not use registered servlet's service.ranking property

[ https://issues.apache.org/jira/browse/SLING-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510658#comment-14510658 ] Felix Meschberger edited comment on SLING-4655 at 4/24/15 8:58 AM

[jira] [Created] (SLING-4655) Servlet Resolver does not use registered servlet's service.ranking property

Felix Meschberger created SLING-4655: Summary: Servlet Resolver does not use registered servlet's service.ranking property Key: SLING-4655 URL: https://issues.apache.org/jira/browse/SLING-4655

  1   2   3   4   5   6   7   8   9   10   >