[jira] [Commented] (SLING-3730) ResourceResolver does not always set the metadata sling.resolutionPath properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052186#comment-14052186 ] Carsten Ziegeler commented on SLING-3730: - While it would be correct to remove the

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3734: --- Component/s: Servlets 'org.apache.sling.api.SlingException: Failed to generate

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3734: --- Affects Version/s: Servlets Post 2.3.4 'org.apache.sling.api.SlingException: Failed

[jira] [Comment Edited] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052203#comment-14052203 ] Bertrand Delacretaz edited comment on SLING-3734 at 7/4/14 6:54 AM:

[jira] [Commented] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052203#comment-14052203 ] Bertrand Delacretaz commented on SLING-3734: There was indeed something about

[jira] [Comment Edited] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052203#comment-14052203 ] Bertrand Delacretaz edited comment on SLING-3734 at 7/4/14 7:00 AM:

OSGi Installer MBean to simplify operations

While looking into the Sling OSGi Installer support I was thinking that it would be helpful to expose an MBean which can provide information like * Current pending installations * Last OSGi installer state - Active, Suspended, Processed * Time of last activity This MBean can then be used by

Re: OSGi Installer MBean to simplify operations

Nice idea - the installer has already the info service so I would expect an MBean to report the same information available through that service. Carsten 2014-07-04 9:10 GMT+02:00 Chetan Mehrotra chetan.mehro...@gmail.com: While looking into the Sling OSGi Installer support I was thinking

[jira] [Resolved] (SLING-3728) MapEntries-aliasMap ds incorrect information in case of alias path removal

[ https://issues.apache.org/jira/browse/SLING-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso resolved SLING-3728. -- Resolution: Fixed Fix Version/s: Resource Resolver 1.1.2 added unit tests and fix in

[jira] [Commented] (SLING-2082) XSS vulnerability: HtmlResponse output does not escape URLs in HTML

[ https://issues.apache.org/jira/browse/SLING-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052237#comment-14052237 ] Bertrand Delacretaz commented on SLING-2082: FWIW here's a curl example that

[jira] [Resolved] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-3734. - Resolution: Fixed Thanks Bertrand for the super-quick fix! This solves the problem for

Re: OSGi Installer MBean to simplify operations

Hi Chetan, On Fri, Jul 4, 2014 at 9:10 AM, Chetan Mehrotra chetan.mehro...@gmail.com wrote: While looking into the Sling OSGi Installer support I was thinking that it would be helpful to expose an MBean... Sounds great - one typical use case that I see, at least in testing, is to copy N

Re: OSGi Installer MBean to simplify operations

Hi Bertrand, On Fri, Jul 4, 2014 at 2:05 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: This testing might happen internally to the Sling instance, so if it's easy to provide the info as a plain OSGi service as we Above information is already available via InfoProvider [1]. The MBean

Re: OSGi Installer MBean to simplify operations

On Fri, Jul 4, 2014 at 11:22 AM, Chetan Mehrotra chetan.mehro...@gmail.com wrote: ...Above information is already available via InfoProvider [1]. The MBean would make use of that only.. ah ok, great! I'll have a look next time I need that kind of info. -Bertrand [1]

[jira] [Updated] (SLING-3735) support JNDI lookup in JDBC DataSource Provider

[ https://issues.apache.org/jira/browse/SLING-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-3735: -- Summary: support JNDI lookup in JDBC DataSource Provider (was: support JNDI lookup in JDBC

[jira] [Created] (SLING-3735) support JNDI lookup in JDBC DatasSource Provider

Julian Reschke created SLING-3735: - Summary: support JNDI lookup in JDBC DatasSource Provider Key: SLING-3735 URL: https://issues.apache.org/jira/browse/SLING-3735 Project: Sling Issue Type:

Combining Sling performance and Sling Junit

Hi, Following the ticket https://issues.apache.org/jira/browse/SLING-3708, I've implemented a first prototype of the combination between the server-side Junit test and the performance testing utilities. The source are available on https://github.com/mtarantino/sling. Here a small description

[jira] [Assigned] (SLING-3735) support JNDI lookup in JDBC DataSource Provider

[ https://issues.apache.org/jira/browse/SLING-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned SLING-3735: -- Assignee: Chetan Mehrotra support JNDI lookup in JDBC DataSource Provider

[jira] [Updated] (SLING-3735) support JNDI lookup in JDBC DataSource Provider

[ https://issues.apache.org/jira/browse/SLING-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-3735: --- Fix Version/s: DataSource Provider 0.0.2 support JNDI lookup in JDBC DataSource Provider

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #630

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/630/

Jenkins build is still unstable: sling-trunk-1.7 #630

See https://builds.apache.org/job/sling-trunk-1.7/changes

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2257

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2257/

Jenkins build is still unstable: sling-trunk-1.6 #2257

See https://builds.apache.org/job/sling-trunk-1.6/changes

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2257

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2257/

[jira] [Created] (SLING-3736) Expose OSGi Installer state via JMX

Chetan Mehrotra created SLING-3736: -- Summary: Expose OSGi Installer state via JMX Key: SLING-3736 URL: https://issues.apache.org/jira/browse/SLING-3736 Project: Sling Issue Type:

[jira] [Updated] (SLING-3736) Expose OSGi Installer state via JMX

[ https://issues.apache.org/jira/browse/SLING-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-3736: --- Attachment: SLING-3736.patch Patch for the same Expose OSGi Installer state via JMX

Re: OSGi Installer MBean to simplify operations

Created SLING-3736 for this with a patch. We can discuss it further there Chetan Mehrotra On Fri, Jul 4, 2014 at 2:54 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Fri, Jul 4, 2014 at 11:22 AM, Chetan Mehrotra chetan.mehro...@gmail.com wrote: ...Above information is already

[jira] [Reopened] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reopened SLING-3710: Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other

[jira] [Commented] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052420#comment-14052420 ] Robert Munteanu commented on SLING-3710: Reopened since I found a case which is

[jira] [Resolved] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3710. Resolution: Fixed Incorrect handling of nt:hierarchyNode instances nested within

[jira] [Commented] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052423#comment-14052423 ] Robert Munteanu commented on SLING-3710: *

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2258

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2258/

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2258

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2258/

Jenkins build is still unstable: sling-trunk-1.6 #2258

See https://builds.apache.org/job/sling-trunk-1.6/changes

RE: [VOTE] Release Apache Sling Scripting JSP 2.1.2 and Apache Sling Scripting Java 2.0.8

+1 Best regards mike -Original Message- From: Carsten Ziegeler [mailto:cziege...@apache.org] Sent: Wednesday, July 02, 2014 1:51 PM To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling Scripting JSP 2.1.2 and Apache Sling Scripting Java 2.0.8 Hi, We solved two

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #631

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/631/

Jenkins build is still unstable: sling-trunk-1.7 #631

See https://builds.apache.org/job/sling-trunk-1.7/changes

[jira] [Commented] (SLING-3732) add an authentication module using Login with XING

[ https://issues.apache.org/jira/browse/SLING-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052534#comment-14052534 ] Oliver Lietz commented on SLING-3732: - initial version of Apache Sling Authentication

[jira] [Commented] (SLING-3731) add an authentication module using XING API with OAuth

[ https://issues.apache.org/jira/browse/SLING-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052533#comment-14052533 ] Oliver Lietz commented on SLING-3731: - initial version of Apache Sling Authentication

[jira] [Created] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

Timothee Maret created SLING-3737: - Summary: Instance Sling Identifier may be randomly reset on restart Key: SLING-3737 URL: https://issues.apache.org/jira/browse/SLING-3737 Project: Sling

[GitHub] sling pull request: SLING-3737 - Instance Sling Identifier may be ...

GitHub user tmaret opened a pull request: https://github.com/apache/sling/pull/22 SLING-3737 - Instance Sling Identifier may be randomly reset on restart * add unit test to cover the use case * read the file completely using org.apache.commons.io.FileUtils * fix the

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[ https://issues.apache.org/jira/browse/SLING-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052546#comment-14052546 ] ASF GitHub Bot commented on SLING-3737: --- GitHub user tmaret opened a pull request:

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[ https://issues.apache.org/jira/browse/SLING-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052547#comment-14052547 ] Timothee Maret commented on SLING-3737: --- Opened pull request with unit test and fix

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[ https://issues.apache.org/jira/browse/SLING-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052549#comment-14052549 ] Timothee Maret commented on SLING-3737: ---

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #632

See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/632/

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2259

See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2259/

Jenkins build is still unstable: sling-trunk-1.6 #2259

See https://builds.apache.org/job/sling-trunk-1.6/changes

[jira] [Commented] (SLING-3737) Instance Sling Identifier may be randomly reset on restart

[ https://issues.apache.org/jira/browse/SLING-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052603#comment-14052603 ] Ian Boston commented on SLING-3737: --- I am +1 on applying this patch, although since I