[jira] [Created] (SLING-3377) Make topology connector a plain HttpServlet instead of a SlingServlet

Stefan Egli created SLING-3377: -- Summary: Make topology connector a plain HttpServlet instead of a SlingServlet Key: SLING-3377 URL: https://issues.apache.org/jira/browse/SLING-3377 Project: Sling

[jira] [Commented] (SLING-3367) gzip topology announcements

[ https://issues.apache.org/jira/browse/SLING-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893181#comment-13893181 ] Stefan Egli commented on SLING-3367: [~marett], agreed. If request-gzip is

[jira] [Commented] (SLING-3377) Make topology connector a plain HttpServlet instead of a SlingServlet

[ https://issues.apache.org/jira/browse/SLING-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893183#comment-13893183 ] Bertrand Delacretaz commented on SLING-3377: Will access control be ok with a

[jira] [Commented] (SLING-3377) Make topology connector a plain HttpServlet instead of a SlingServlet

[ https://issues.apache.org/jira/browse/SLING-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893193#comment-13893193 ] Stefan Egli commented on SLING-3377: Yes. The topology connector is currently

[jira] [Resolved] (SLING-3332) Long startup time with many sling:alias

[ https://issues.apache.org/jira/browse/SLING-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso resolved SLING-3332. -- Resolution: Fixed Fix Version/s: Resource Resolver 1.1.0 applied patch as discussed in

[featureflags] NPE in context.getResourceResolver()

Hi all mates, A colleague of mine just let me notice that from the sling ExecutionContextImpl implementation, it seems like resourceResolver could be null, SlingAuthenticator gets control after the Feature’s filter sets the resolver... Is there any way we can obtain the ResourceResolver before

Re: [featureflags] NPE in context.getResourceResolver()

Hi Am 06.02.2014 um 11:18 schrieb Simone Tripodi simonetrip...@apache.org: Hi all mates, A colleague of mine just let me notice that from the sling ExecutionContextImpl implementation, it seems like resourceResolver could be null, Well yes, that is how ExecutionContext.getResourceResolver

[jira] [Commented] (SLING-2529) Add support for JCR Observation event types: NODE_MOVED and PERSIST

[ https://issues.apache.org/jira/browse/SLING-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893250#comment-13893250 ] Felix Meschberger commented on SLING-2529: -- [~sparktronics] The problem with the

[jira] [Created] (SLING-3378) SelectorFormServlet should escape auth type

Bertrand Delacretaz created SLING-3378: -- Summary: SelectorFormServlet should escape auth type Key: SLING-3378 URL: https://issues.apache.org/jira/browse/SLING-3378 Project: Sling Issue

[jira] [Resolved] (SLING-3378) SelectorFormServlet should escape auth type

[ https://issues.apache.org/jira/browse/SLING-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3378. Resolution: Fixed Fixed in revision 1565165 SelectorFormServlet should escape

buildbot failure in ASF Buildbot on sling-trunk

The Buildbot has detected a new failure on builder sling-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk/builds/250 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

buildbot success in ASF Buildbot on sling-trunk

The Buildbot has detected a restored build on builder sling-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk/builds/252 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

RE: [featureflags] NPE in context.getResourceResolver()

Hi Felix, I saw this briefly. This comes if I try to use web console to see the list of features. In that case, if the isEnabled depends on resourceResolver that will perhaps fails. Thanks, -Amit -Original Message- From: Felix Meschberger [mailto:fmesc...@adobe.com] Sent: 06

[jira] [Created] (SLING-3379) OptingServlet accepts method bypassed

Anthony Rumsey created SLING-3379: - Summary: OptingServlet accepts method bypassed Key: SLING-3379 URL: https://issues.apache.org/jira/browse/SLING-3379 Project: Sling Issue Type: Bug

[jira] [Updated] (SLING-3379) OptingServlet accepts method bypassed

[ https://issues.apache.org/jira/browse/SLING-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Rumsey updated SLING-3379: -- Component/s: Servlets OptingServlet accepts method bypassed

[jira] [Commented] (SLING-3379) OptingServlet accepts method bypassed

[ https://issues.apache.org/jira/browse/SLING-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893433#comment-13893433 ] Anthony Rumsey commented on SLING-3379: --- If I am not mistaken, this is what is going

buildbot failure in ASF Buildbot on sling-trunk

The Buildbot has detected a new failure on builder sling-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk/builds/253 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

[jira] [Resolved] (SLING-3377) Make topology connector a plain HttpServlet instead of a SlingServlet

[ https://issues.apache.org/jira/browse/SLING-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3377. Resolution: Fixed Make topology connector a plain HttpServlet instead of a SlingServlet

[jira] [Resolved] (SLING-3367) gzip topology announcements

[ https://issues.apache.org/jira/browse/SLING-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3367. Resolution: Fixed fixed. response-zipping now happens client-controlled (via Accept-Encoding) -

[jira] [Resolved] (SLING-3375) HttpClient use in org.apache.sling.discovery.impl package does not close method connections explicitely

[ https://issues.apache.org/jira/browse/SLING-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3375. Resolution: Fixed HttpClient use in org.apache.sling.discovery.impl package does not close

buildbot success in ASF Buildbot on sling-trunk

The Buildbot has detected a restored build on builder sling-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk/builds/254 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

[VOTE RESULT] Release Service User Mapper 1.0.0

The vote passed with three binding +1 votes from Felix Meschberger, Justin Edelson, and Carsten Ziegeler Thanks everyone for voting Carsten -- Carsten Ziegeler cziege...@apache.org

Re: [VOTE] Release Apache Sling JCR API 2.2.0, JCR Base 2.2.0 and JCR Resource 2.3.0

We're missing some binding votes here, anyone? Thanks Carsten 2014-01-30 21:19 GMT+01:00 Oliver Lietz apa...@oliverlietz.de: Am Donnerstag, 30. Januar 2014 schrieb Carsten Ziegeler: Hi, this vote is about three related modules in the jcr space, apart from bug fixes it contains the

[VOTE RESULT] Release Testing Resource Resolver Mock 0.2.0

The vote passed with three binding +1 votes from Bertrand Delacretaz, Carsten Ziegeler, and Felix Meschberger Thanks Carsten -- Carsten Ziegeler cziege...@apache.org

[jira] [Updated] (SLING-3320) Execution order of BindingsValuesProvider

[ https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-3320: Attachment: SLING-3320_1.diff I've attached a patch that uses the natural ordering of the BVPs'

SLING-3320 Execution order of BindingsValuesProvider

Hi, I've attached a patch [1] for SLING-3320 [2]. Could somebody please review it and eventually apply it to trunk? Thanks, Radu [1] - https://issues.apache.org/jira/secure/attachment/12627387/SLING-3320_1.diff [2] - https://issues.apache.org/jira/browse/SLING-3320

[jira] [Updated] (SLING-3352) Expose OSGI configuration via HTTP

[ https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3352: Summary: Expose OSGI configuration via HTTP (was: Expose OSGI configuration as JCR nodes)

[jira] [Assigned] (SLING-3352) Expose OSGI configuration as JCR nodes

[ https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3352: --- Assignee: Carsten Ziegeler Expose OSGI configuration as JCR nodes

[jira] [Commented] (SLING-3352) Expose OSGI configuration via HTTP

[ https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893648#comment-13893648 ] Carsten Ziegeler commented on SLING-3352: - I've just updated the title of this

[jira] [Created] (SLING-3380) Reduce memory footprint of

Michael Dürig created SLING-3380: Summary: Reduce memory footprint of Key: SLING-3380 URL: https://issues.apache.org/jira/browse/SLING-3380 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-2529) Add support for JCR Observation event types: NODE_MOVED and PERSIST

[ https://issues.apache.org/jira/browse/SLING-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893849#comment-13893849 ] Mario Rodriguez Jaen commented on SLING-2529: - The change will also require to

[jira] [Commented] (SLING-3380) Reduce memory footprint of

[ https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893891#comment-13893891 ] Alexander Klimetschek commented on SLING-3380: -- You might want to finish the

[jira] [Commented] (SLING-2393) Update Post Servlet Documentation for patch operation

[ https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894208#comment-13894208 ] Alexander Klimetschek commented on SLING-2393: -- Ping... this would be nice

[jira] [Created] (SLING-3381) JobManager.getQueue() might not return queue

Carsten Ziegeler created SLING-3381: --- Summary: JobManager.getQueue() might not return queue Key: SLING-3381 URL: https://issues.apache.org/jira/browse/SLING-3381 Project: Sling Issue Type:

[jira] [Resolved] (SLING-3381) JobManager.getQueue() might not return queue

[ https://issues.apache.org/jira/browse/SLING-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3381. - Resolution: Fixed Fixed by applying the filtering in all places JobManager.getQueue()