[jira] [Created] (SLING-5650) Extract Common Code into a Framework with IDE hooks

[Andreas Schaefer (JIRA)]

Andreas Schaefer created SLING-5650:
---

 Summary: Extract Common Code into a Framework with IDE hooks
 Key: SLING-5650
 URL: https://issues.apache.org/jira/browse/SLING-5650
 Project: Sling
  Issue Type: Improvement
  Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.10
Reporter: Andreas Schaefer


Module Deployment, Support Bundle installation etc is a mixture of IDE and 
Non-IDE code. It would be great to extract the Non-IDE code into a Framework 
that provides hooks for IDEs to integrate.
The current IntelliJ Sling IDE plugin has a prototype to illustrate that but is 
not truly IDE independent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5649) Non-Eclipse Modules should not depend on Eclipse Depedencies

[Andreas Schaefer (JIRA)]

Andreas Schaefer created SLING-5649:
---

 Summary: Non-Eclipse Modules should not depend on Eclipse 
Depedencies
 Key: SLING-5649
 URL: https://issues.apache.org/jira/browse/SLING-5649
 Project: Sling
  Issue Type: Improvement
  Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.10
Reporter: Andreas Schaefer


Currently modules like api, artifacts, imll-resource, impl-vlt have their 
depends obtained using Tycho which depends on the supported Eclipse version.
Other IDEs like IntelliJ IDEA cannot handle that and so development is 
difficult and time consuming.
Also other IDEs that do not use OSGi might have an issue when Eclipse version 
changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5648) Make Non-Eclipse Module regular Maven Packages

[Andreas Schaefer (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Schaefer updated SLING-5648:

Issue Type: Improvement  (was: Bug)

> Make Non-Eclipse Module regular Maven Packages
> --
>
> Key: SLING-5648
> URL: https://issues.apache.org/jira/browse/SLING-5648
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.10
>Reporter: Andreas Schaefer
>
> Non Eclipse modules like api, artifacts, imll-resource, impl-vlt should be 
> regular Maven packages (jar) instead of eclipse plugins (eclipse-plugin) to 
> support development of it by other IDEs like IntelliJ IDEA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5648) Make Non-Eclipse Module regular Maven Packages

[Andreas Schaefer (JIRA)]

Andreas Schaefer created SLING-5648:
---

 Summary: Make Non-Eclipse Module regular Maven Packages
 Key: SLING-5648
 URL: https://issues.apache.org/jira/browse/SLING-5648
 Project: Sling
  Issue Type: Bug
  Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.10
Reporter: Andreas Schaefer


Non Eclipse modules like api, artifacts, imll-resource, impl-vlt should be 
regular Maven packages (jar) instead of eclipse plugins (eclipse-plugin) to 
support development of it by other IDEs like IntelliJ IDEA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Crankstart IT tests.

[Ian Boston]

Hi,
I am trying to use

public class LauncherIT {

@ClassRule
public static CrankstartSetup crankstartSetup = new
CrankstartSetup().withModelResources(
"/crankstart-model.txt",
"/provisioning-model/base.txt",
"/provisioning-model/jobs-runtime.txt",
"/provisioning-model/crankstart-test-support.txt");

...


in a Junit test, but the crankstartSetup.before() is not called, hence the
crankstart never starts.

Running org.apache.sling.crankstart.launcher.BasicLauncherIT in the same
environment (IntelliJ) the before() is called.

The maven project containing the code is at [1], largely copied from
BasicLauncherIT.

any pointers ?

Best Regards
Ian



1
https://github.com/ieb/sling/blob/jobs_28/contrib/extensions/jobs/it/src/test/java/org/apache/sling/jobs/it/LauncherIT.java

Re: [VOTE] Release Apache Sling Servlets Post 2.3.10

[Robert Munteanu]

On Thu, 2016-04-07 at 10:05 +0200, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[jira] [Closed] (SLING-5622) Deadlock between service unregister (thus unbindTopologyEventListener) and discoveryLiteCheck

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler closed SLING-5622.
---

> Deadlock between service unregister (thus unbindTopologyEventListener) and 
> discoveryLiteCheck
> -
>
> Key: SLING-5622
> URL: https://issues.apache.org/jira/browse/SLING-5622
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Resource Resolver 1.4.8, Discovery Oak 1.2.6
> Environment: discovery.oak 1.2.6
> resourceresolver 1.4.8
>Reporter: Stefan Egli
>Assignee: Carsten Ziegeler
>Priority: Critical
> Fix For: Resource Resolver 1.4.10
>
>
> There's a java level deadlock between the following two threads, excerpts 
> below. It's not yet clear if this is an issue of discovery.oak or 
> resourceresolver.
> thread 1:
> {noformat}
> "LeaseFailureHandler-Thread" daemon prio=5 tid=0x7f34 nid=0x in 
> Object.wait()
>java.lang.Thread.State: WAITING (on object monitor)
> at sun.misc.Unsafe.park(Native Method)
> - waiting to lock <0x575a7644> (a 
> java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by 
> "discovery.connectors.common.runner.e8dd34be-8886-4e5d-891f-5509b4dea0f0.discoveryLiteChec
> k" tid=0x4,330
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
> at 
> java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214)
> at 
> java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290)
> at 
> org.apache.sling.discovery.oak.OakDiscoveryService.unbindTopologyEventListener(OakDiscoveryService.java:368)
> ...
> at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:144)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.unregisterFactory(ResourceResolverFactoryActivator.java:611)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.unregisterFactory(ResourceResolverFactoryActivator.java:602)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.checkFactoryPreconditions(ResourceResolverFactoryActivator.java:674)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.access$100(ResourceResolverFactoryActivator.java:79)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator$1.providerRemoved(ResourceResolverFactoryActivator.java:500)
> at 
> org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker.unregister(ResourceProviderTracker.java:224)
> - locked <0x35cd7613> (a java.util.HashMap)
> at 
> org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker.access$100(ResourceProviderTracker.java:58)
> at 
> org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker$1.removedService(ResourceProviderTracker.java:109)
> ...
> at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:144)
> at 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.unregisterService(AbstractSlingRepositoryManager.java:262)
> at 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.stop(AbstractSlingRepositoryManager.java:389)
> ...
> at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:1038)
> at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:1024)
> at 
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService$1.handleLeaseFailure(DocumentNodeStoreService.java:413)
> at 
> org.apache.jackrabbit.oak.plugins.document.ClusterNodeInfo$1.run(ClusterNodeInfo.java:696)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - locked <0x4402f4fd> (a 
> java.util.concurrent.locks.ReentrantLock$FairSync)
> - locked <0x1e2230ed> (a 
> java.util.concurrent.locks.ReentrantLock$FairSync)
> - locked <0x56ba270f> (a 
> java.util.concurrent.locks.ReentrantLock$FairSync)
> {noformat}
> and thread 2:
> {noformat}
> "discovery.connectors.common.runner.e8dd34be-8886-4e5d-891f-5509b4dea0f0.discoveryLiteCheck"
>  daemon prio=5 tid=0x10ea nid=0x waiting for monitor entry
>java.lang.Thread.State: BLOCKED
> at 
> 

[jira] [Closed] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler closed SLING-5602.
---

> The Discovery module does not work any more after a ResourceResolverFactory 
> reactivation
> 
>
> Key: SLING-5602
> URL: https://issues.apache.org/jira/browse/SLING-5602
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.8
>Reporter: Radu Cotescu
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: Resource Resolver 1.4.10
>
>
> The Discovery module does not work any more after the Resource Resolver 
> Factory is reconfigured. To reproduce this start the latest launchpad (built 
> from 
> https://github.com/apache/sling/blob/c441d5b672d1952a82a1c9fe1e6d81e86cec0018/launchpad/builder/src/main/provisioning/sling.txt)
>  and then:
> # go to 
> http://localhost:8080/system/console/configMgr/org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl
> # click on save (this will trigger the component's reactivation)
> # check the error log
> {noformat}
> 14.03.2016 16:29:57.331 *ERROR* 
> [discovery.connectors.common.runner.7fd8d00a-802a-4367-a384-64024e28dbbc.discoveryLiteCheck]
>  org.apache.sling.discovery.oak.cluster.OakClusterViewService 
> getLocalClusterView: repository exception: java.lang.Exception: Could not 
> adapt resourceResolver to session: 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl@499d9cc9
> java.lang.Exception: Could not adapt resourceResolver to session: 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl@499d9cc9
>   at 
> org.apache.sling.discovery.commons.providers.spi.base.DiscoveryLiteDescriptor.getDescriptorFrom(DiscoveryLiteDescriptor.java:41)
>   at 
> org.apache.sling.discovery.oak.cluster.OakClusterViewService.getLocalClusterView(OakClusterViewService.java:111)
>   at 
> org.apache.sling.discovery.base.commons.BaseDiscoveryService.getTopology(BaseDiscoveryService.java:77)
>   at 
> org.apache.sling.discovery.oak.OakDiscoveryService.checkForTopologyChange(OakDiscoveryService.java:657)
>   at 
> org.apache.sling.discovery.oak.pinger.OakViewChecker.discoveryLiteCheck(OakViewChecker.java:232)
>   at 
> org.apache.sling.discovery.oak.pinger.OakViewChecker.access$000(OakViewChecker.java:64)
>   at 
> org.apache.sling.discovery.oak.pinger.OakViewChecker$1.run(OakViewChecker.java:208)
>   at 
> org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.safelyRun(PeriodicBackgroundJob.java:86)
>   at 
> org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.run(PeriodicBackgroundJob.java:77)
>   at java.lang.Thread.run(Thread.java:745)
> 14.03.2016 16:29:57.332 *INFO* 
> [discovery.connectors.common.runner.7fd8d00a-802a-4367-a384-64024e28dbbc.discoveryLiteCheck]
>  org.apache.sling.discovery.base.commons.BaseDiscoveryService getTopology: 
> undefined cluster view: REPOSITORY_EXCEPTION] 
> org.apache.sling.discovery.base.commons.UndefinedClusterViewException: 
> Exception while processing descriptor: java.lang.Exception: Could not adapt 
> resourceResolver to session: 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl@499d9cc9
> 14.03.2016 16:29:57.332 *INFO* 
> [discovery.connectors.common.runner.7fd8d00a-802a-4367-a384-64024e28dbbc.discoveryLiteCheck]
>  org.apache.sling.discovery.commons.providers.base.ViewStateManagerImpl 
> enqueueForAll: sending topologyEvent TopologyEvent [type=TOPOLOGY_CHANGING, 
> oldView=DefaultTopologyView[current=false, num=1, 
> instances=7fd8d00a-802a-4367-a384-64024e28dbbc[local=true,leader=true]], 
> newView=null], to all (5) listeners
> 14.03.2016 16:29:57.332 *ERROR* [Discovery-AsyncEventSender] 
> org.apache.sling.discovery.oak.TopologyWebConsolePlugin 
> addDiscoveryLiteHistoryEntry: Exception: java.lang.Exception: Could not adapt 
> resourceResolver to session: 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl@149e86f0
> java.lang.Exception: Could not adapt resourceResolver to session: 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl@149e86f0
>   at 
> org.apache.sling.discovery.commons.providers.spi.base.DiscoveryLiteDescriptor.getDescriptorFrom(DiscoveryLiteDescriptor.java:41)
>   at 
> org.apache.sling.discovery.oak.TopologyWebConsolePlugin.updateDiscoveryLiteHistory(TopologyWebConsolePlugin.java:771)
>   at 
> org.apache.sling.discovery.oak.TopologyWebConsolePlugin.handleTopologyEvent(TopologyWebConsolePlugin.java:722)
>   at 
> org.apache.sling.discovery.commons.providers.base.AsyncTopologyEvent.trigger(AsyncTopologyEvent.java:53)
>   at 
> org.apache.sling.discovery.commons.providers.base.AsyncEventSender.run(AsyncEventSender.java:118)
>   

[VOTE RESULT] Release Apache Sling Resource Resolver 1.4.10

[Carsten Ziegeler]

The vote passed with four binding +1 votes.

 Thanks
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Servlets Post 2.3.10

[Stefan Egli]

+1

Cheers,
Stefan

On 07/04/16 10:05, "Carsten Ziegeler"  wrote:

>Hi,
>
>We solved 2 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12332788
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1452
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1452 /tmp/sling-staging
>
>Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
>This majority vote is open for at least 72 hours.
>
>Regards
>Carsten
>-- 
>Carsten Ziegeler
>Adobe Research Switzerland
>cziege...@apache.org

Re: Java 8 for launchpad?

[Peter Hunsberger]

I believe IBM is dropping support for Websphere 8.0 sometime this summer...

Peter Hunsberger

On Thu, Apr 7, 2016 at 7:20 AM, Robert Munteanu  wrote:

> On Thu, 2016-04-07 at 08:18 +0200, Carsten Ziegeler wrote:
> > Hi,
> >
> > the latest Apache Felix Http Jetty release is embedding latest Jetty
> > version which requires Java 8.
> >
> > The question is now, do we want to update to that version? And if we
> > do
> > so are we fine with using Java as the base for launchpad and then
> > ultimately for our users?
>
> +1 for Java 8.
>
> Note that right now the default Java version for modules is 6, with 10
> bundles ( including commons/compiler, extensions/event and
> installer/providers/file ) requiring Java 7 and 4 bundles requiring
> Java 8 ( validation bundles and fling sample ).
>
> Maybe we should also open up the discussion of moving to Java 7 and
> droppping Java 6 support. Oracle discontinued public support for Java 6
> in Feb 2013. IBM is AFAIK still supporting it for Websphere 8.0, this
> means that we will require Websphere 8.5 for WAR deployments ( which is
> OK I guess... )
>
> Robert
>

Re: Java 8 for launchpad?

[Robert Munteanu]

On Thu, 2016-04-07 at 08:18 +0200, Carsten Ziegeler wrote:
> Hi,
> 
> the latest Apache Felix Http Jetty release is embedding latest Jetty
> version which requires Java 8.
> 
> The question is now, do we want to update to that version? And if we
> do
> so are we fine with using Java as the base for launchpad and then
> ultimately for our users?

+1 for Java 8.

Note that right now the default Java version for modules is 6, with 10
bundles ( including commons/compiler, extensions/event and
installer/providers/file ) requiring Java 7 and 4 bundles requiring
Java 8 ( validation bundles and fling sample ).

Maybe we should also open up the discussion of moving to Java 7 and
droppping Java 6 support. Oracle discontinued public support for Java 6
in Feb 2013. IBM is AFAIK still supporting it for Websphere 8.0, this
means that we will require Websphere 8.5 for WAR deployments ( which is
OK I guess... )

Robert

[jira] [Commented] (SLING-5647) Provide ActiveMQ implementation of the MoM API in SLING-5646

[Ian Boston (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230117#comment-15230117
 ] 

Ian Boston commented on SLING-5647:
---

See https://github.com/ieb/sling/tree/jobs_28/contrib/extensions/jobs/activemq 
for PoC covering the Out of the Box use case. Needs work to cover the other use 
cases.

> Provide ActiveMQ implementation of the MoM API in SLING-5646
> 
>
> Key: SLING-5647
> URL: https://issues.apache.org/jira/browse/SLING-5647
> Project: Sling
>  Issue Type: Sub-task
>Reporter: Ian Boston
>Assignee: Ian Boston
>
> Provide a default implementation of the MoM API in SLING-5646 using ActiveMQ. 
> The bundle must create and start a running ActiveMQ server without additional 
> intervention and configuration. Ideally the bundle should work in a cluster 
> embedding an ActiveMQ broker into each Sling instance, and ideally the bundle 
> should be able to integrate with an existing ActiveMQ cluster. Based on AMQ 
> documentation all are possible via configuration and no code changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230115#comment-15230115
 ] 

Bertrand Delacretaz commented on SLING-5643:


I would be more comfortable having this under /contrib to start with, it can 
always move under commons later.

Would that work for you [~olli] ?

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5647) Provide ActiveMQ implementation of the MoM API in SLING-5646

[Ian Boston (JIRA)]

Ian Boston created SLING-5647:
-

 Summary: Provide ActiveMQ implementation of the MoM API in 
SLING-5646
 Key: SLING-5647
 URL: https://issues.apache.org/jira/browse/SLING-5647
 Project: Sling
  Issue Type: Sub-task
Reporter: Ian Boston


Provide a default implementation of the MoM API in SLING-5646 using ActiveMQ. 
The bundle must create and start a running ActiveMQ server without additional 
intervention and configuration. Ideally the bundle should work in a cluster 
embedding an ActiveMQ broker into each Sling instance, and ideally the bundle 
should be able to integrate with an existing ActiveMQ cluster. Based on AMQ 
documentation all are possible via configuration and no code changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5647) Provide ActiveMQ implementation of the MoM API in SLING-5646

[Ian Boston (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ian Boston reassigned SLING-5647:
-

Assignee: Ian Boston

> Provide ActiveMQ implementation of the MoM API in SLING-5646
> 
>
> Key: SLING-5647
> URL: https://issues.apache.org/jira/browse/SLING-5647
> Project: Sling
>  Issue Type: Sub-task
>Reporter: Ian Boston
>Assignee: Ian Boston
>
> Provide a default implementation of the MoM API in SLING-5646 using ActiveMQ. 
> The bundle must create and start a running ActiveMQ server without additional 
> intervention and configuration. Ideally the bundle should work in a cluster 
> embedding an ActiveMQ broker into each Sling instance, and ideally the bundle 
> should be able to integrate with an existing ActiveMQ cluster. Based on AMQ 
> documentation all are possible via configuration and no code changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230112#comment-15230112
 ] 

Oliver Lietz commented on SLING-5643:
-

{quote}
How to you handle different implementations? The example in the README looks 
nice, but I guess in practice deciding on a string (email vs phone number) to 
select the right service does not really work.
{quote}

Right, using target filters is my preferred option here.

{quote}
What about using Promises instead of Futures?
{quote}

+1, this was some old code lain around which can be further improved and 
adjusted using Java 8 features indeed

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5646) Provide Message oriented Middleware API to support implementation of distributed Jobs API

[Ian Boston (JIRA)]

Ian Boston created SLING-5646:
-

 Summary: Provide Message oriented Middleware API to support 
implementation of distributed Jobs API
 Key: SLING-5646
 URL: https://issues.apache.org/jira/browse/SLING-5646
 Project: Sling
  Issue Type: Sub-task
Reporter: Ian Boston
Assignee: Ian Boston


See PoC at 
https://github.com/ieb/sling/tree/jobs_28/contrib/extensions/jobs/mom-api

Needs to support Pub/Sub style messaging and Queue messaging.
Must not depend on Jobs API and must not bind to a specific technology.
Implementations are expected to be JMS or AMPQ based with an initial 
implementation based on ActiveMQ.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5645) Provide a Jobs API and implementation suitable for widely distributed job processing.

[Ian Boston (JIRA)]

Ian Boston created SLING-5645:
-

 Summary: Provide a Jobs API and implementation suitable for widely 
distributed job processing.
 Key: SLING-5645
 URL: https://issues.apache.org/jira/browse/SLING-5645
 Project: Sling
  Issue Type: New Feature
Reporter: Ian Boston
Assignee: Ian Boston


This issue is to track work on a proof of concept to create a Jobs API and 
implementation that will work in a distributed environment where the job 
submitters and job consumers are not necessarily in the same JVM or in the same 
Sling cluster. 

Work is being done in a branch at 
https://github.com/ieb/sling/tree/jobs_28/contrib/extensions/jobs


Since the implementation needs supporting APIs/Capabilities not already present 
in Sling. There are some sub-tasks associated with this issue to address those.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230097#comment-15230097
 ] 

Carsten Ziegeler commented on SLING-5643:
-

How to you handle different implementations? The example in the README looks 
nice, but I guess in practice deciding on a string (email vs phone number) to 
select the right service does not really work.

What about using Promises instead of Futures?

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230092#comment-15230092
 ] 

Oliver Lietz commented on SLING-5643:
-

It's possible to use EventAdmin and EventListener of course but neither do we 
have a default implementation nor can you handle the result easily. OSGi Events 
are not the silver bullet (nor is Apache Camel).

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-5643) Provide a simple messaging API

[Chetan Mehrotra (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230068#comment-15230068
 ] 

Chetan Mehrotra edited comment on SLING-5643 at 4/7/16 10:49 AM:
-

I saw the mail example but same thing can be done by binding a mail listener to 
a specific topic can send a message via EventListener and send message via 
EventAdmin [1]. So was wondering if we need a complete new API here and hence 
the interest in broader usecase

[1] 
http://felix.apache.org/documentation/subprojects/apache-felix-event-admin.html


was (Author: chetanm):
I saw the mail example but same thing can be done by binding a mail listener to 
a specific topic can send a message via EventListener. So was wondering if we 
need a complete new API here and hence the interest in broader usecase

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Chetan Mehrotra (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230068#comment-15230068
 ] 

Chetan Mehrotra commented on SLING-5643:


I saw the mail example but same thing can be done by binding a mail listener to 
a specific topic can send a message via EventListener. So was wondering if we 
need a complete new API here and hence the interest in broader usecase

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230064#comment-15230064
 ] 

Oliver Lietz commented on SLING-5643:
-

[~chetanm], have a look at the 
[README|https://github.com/apache/sling/blob/trunk/bundles/commons/org.apache.sling.commons.messaging/README.md].
You can use any kind of protocol/technology to send messages as the API is very 
simple. I've added an [implementation based on Commons 
Email|https://github.com/apache/sling/tree/trunk/bundles/commons/org.apache.sling.commons.messaging.mail]
 to send messages with SMTP already.

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Chetan Mehrotra (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230019#comment-15230019
 ] 

Chetan Mehrotra commented on SLING-5643:


[~olli] Any details around usecase for this new API. What kind of usage you 
have in mind? How does it compare against OSGi Event post against specific 
topic. Might be good to discuss this on DL

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5644) Provide an messaging implementation based on Commons Email

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229984#comment-15229984
 ] 

Oliver Lietz commented on SLING-5644:
-

initial commit in [r1738114|https://svn.apache.org/r1738114]

> Provide an messaging implementation based on Commons Email
> --
>
> Key: SLING-5644
> URL: https://issues.apache.org/jira/browse/SLING-5644
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging Mail 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5643) Provide a simple messaging API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229983#comment-15229983
 ] 

Oliver Lietz commented on SLING-5643:
-

initial commit in [r1738113|https://svn.apache.org/r1738113]

> Provide a simple messaging API
> --
>
> Key: SLING-5643
> URL: https://issues.apache.org/jira/browse/SLING-5643
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Messaging 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5638) Sling:alias property not working if user does not have read access to the root node

[Antonio Sanso (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229975#comment-15229975
 ] 

Antonio Sanso commented on SLING-5638:
--

[~bdelacretaz] done thanks. I did not know the root cause when I opened the 
issue :)

> Sling:alias property not working if user does not have read access to the 
> root node
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Java 8 for launchpad?

[Bertrand Delacretaz]

Hi,

On Thu, Apr 7, 2016 at 8:18 AM, Carsten Ziegeler  wrote:
> ...are we fine with using Java as the base for launchpad and then
> ultimately for our users?...

I'm ok as far as the launchpad is concerned, OTOH we have lots of
stable modules which work fine with Java 7 and where moving to Java 8
brings nothing. So those can stay backwards compatible which is often
useful.

So IMO we should keep a working Java 7 build, even if it won't be able
to run the launchpad anymore, and maybe create a java7 Maven profile
to omit some modules for that build.

-Bertrand

[jira] [Updated] (SLING-5638) Sling:alias property not working if user does not have read access to the root node

[Antonio Sanso (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Antonio Sanso updated SLING-5638:
-
Summary: Sling:alias property not working if user does not have read access 
to the root node  (was: Sling:alias property not working if user is having read 
only access to /content folder.)

> Sling:alias property not working if user does not have read access to the 
> root node
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5644) Provide an messaging implementation based on Commons Email

[Oliver Lietz (JIRA)]

Oliver Lietz created SLING-5644:
---

 Summary: Provide an messaging implementation based on Commons Email
 Key: SLING-5644
 URL: https://issues.apache.org/jira/browse/SLING-5644
 Project: Sling
  Issue Type: New Feature
  Components: Commons
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Commons Messaging Mail 1.0.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5643) Provide a simple messaging API

[Oliver Lietz (JIRA)]

Oliver Lietz created SLING-5643:
---

 Summary: Provide a simple messaging API
 Key: SLING-5643
 URL: https://issues.apache.org/jira/browse/SLING-5643
 Project: Sling
  Issue Type: New Feature
  Components: Commons
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Commons Messaging 1.0.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5638) Sling:alias property not working if user is having read only access to /content folder.

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229962#comment-15229962
 ] 

Bertrand Delacretaz commented on SLING-5638:


I agree that this is a bug (and we should have a test for it). 

You might want to update this issues' title and description for clarity then.

> Sling:alias property not working if user is having read only access to 
> /content folder.
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5638) Sling:alias property not working if user is having read only access to /content folder.

[Antonio Sanso (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229948#comment-15229948
 ] 

Antonio Sanso commented on SLING-5638:
--

[~bdelacretaz] from the snippet I pasted above looks like that in order the 
alias to work the user need to have read access on '/' . This is a big IMHO

> Sling:alias property not working if user is having read only access to 
> /content folder.
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-5638) Sling:alias property not working if user is having read only access to /content folder.

[Antonio Sanso (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229948#comment-15229948
 ] 

Antonio Sanso edited comment on SLING-5638 at 4/7/16 9:02 AM:
--

[~bdelacretaz] from the snippet I pasted above looks like that in order the 
alias to work the user need to have read access on '/' . This is a bug IMHO


was (Author: asanso):
[~bdelacretaz] from the snippet I pasted above looks like that in order the 
alias to work the user need to have read access on '/' . This is a big IMHO

> Sling:alias property not working if user is having read only access to 
> /content folder.
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5638) Sling:alias property not working if user is having read only access to /content folder.

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229938#comment-15229938
 ] 

Bertrand Delacretaz commented on SLING-5638:


I'm a bit confused by "read only access to /content", isn't it rather that the 
alias does not work _if the user does not have read access to the root node_? 

> Sling:alias property not working if user is having read only access to 
> /content folder.
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5638) Sling:alias property not working if user is having read only access to /content folder.

[Antonio Sanso (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229908#comment-15229908
 ] 

Antonio Sanso commented on SLING-5638:
--

The culprit is in the ResourceResolverImpl#resolveInternal

{code}
// no direct resource found, so we have to drill down into the
// resource tree to find a match
resource = getAbsoluteResourceInternal(null, "/", parameters, true);
{code}

this wrongly assumes that the session has reading privileges in "/"

> Sling:alias property not working if user is having read only access to 
> /content folder.
> ---
>
> Key: SLING-5638
> URL: https://issues.apache.org/jira/browse/SLING-5638
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>
> issue ;- Sling:alias property not working if user is having read only access 
> to /content folder.
> Steps :-
> 1) Login using admin/admin.
> 2) Create page say mypage.html and provide sling:alias property say 
> mypagealias.
> 3) Create test user and provide read only access on /content folder from 
> useradmin console.
> 4) log out from admin user.
> 5) Hit the page http://localhost:4502/content//mypage.html it 
> will ask for the login ( login as test user ) it opens the page
> 6) hit the alias page 
> http://localhost:4502/content//mypagealias.html - it wont work.
> sling:alias property get stored at jcr:content node for the page in /content, 
> so user with read access on /content should access it. please correct me in 
> case I am missing something.
> to make it work user has to give root( read only ) access to test user only 
> then test user can access alias page. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Servlets Post 2.3.10

[Carsten Ziegeler]

+1


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

[VOTE] Release Apache Sling Servlets Post 2.3.10

[Carsten Ziegeler]

Hi,

We solved 2 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12332788

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1452

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1452 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Resolved] (SLING-5637) Resource.delete is not called if resource is adaptable to Node

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-5637.
-
Resolution: Fixed
  Assignee: Carsten Ziegeler

Applied the patch

> Resource.delete is not called if resource is adaptable to Node
> --
>
> Key: SLING-5637
> URL: https://issues.apache.org/jira/browse/SLING-5637
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.3.8
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.10
>
>
> If a resource is adaptable to Node, the node is directly removed.
> ResourceProvider.delete is never invoked.
> While this works with the JcrResourceProvider it does not work with any other 
> resource provider providing resources which adapt to a node
> Proposed solution:
> {code}
> ### Eclipse Workspace Patch 1.0
> #P org.apache.sling.servlets.post
> Index: 
> src/main/java/org/apache/sling/servlets/post/impl/operations/DeleteOperation.java
> ===
> --- 
> src/main/java/org/apache/sling/servlets/post/impl/operations/DeleteOperation.java
>  (Revision 1737673)
> +++ 
> src/main/java/org/apache/sling/servlets/post/impl/operations/DeleteOperation.java
>  (Arbeitskopie)
> @@ -58,15 +58,15 @@
>  // SLING-3203: selectors, extension and suffix make no sense here and
>  // might lead to deleting other resources than the one the user 
> means.
>  final RequestPathInfo rpi = request.getRequestPathInfo();
> -if( (rpi.getSelectors() != null && rpi.getSelectors().length > 0) 
> +if( (rpi.getSelectors() != null && rpi.getSelectors().length > 0)
>  || (rpi.getExtension() != null && 
> rpi.getExtension().length() > 0)
>  || (rpi.getSuffix() != null && rpi.getSuffix().length() > 
> 0)) {
>  response.setStatus(
> -HttpServletResponse.SC_FORBIDDEN, 
> +HttpServletResponse.SC_FORBIDDEN,
>  "DeleteOperation request cannot include any selectors, 
> extension or suffix");
>  return;
>  }
> -
> +
>  final VersioningConfiguration versioningConfiguration = 
> getVersioningConfiguration(request);
>  final boolean deleteChunks = isDeleteChunkRequest(request);
>  final Iterator res = getApplyToResources(request);
> @@ -100,19 +100,17 @@
>  } else {
>  checkoutIfNecessary(node.getParent(), changes,
>  versioningConfiguration);
> -node.remove();
>  }
> -
> -} else {
> -try {
> -resource.getResourceResolver().delete(resource);
> -} catch (final PersistenceException pe) {
> -if (pe.getCause() instanceof RepositoryException) {
> -throw (RepositoryException) pe.getCause();
> -}
> -throw new RepositoryException(pe);
> +}
> +try {
> +resource.getResourceResolver().delete(resource);
> +} catch (final PersistenceException pe) {
> +if (pe.getCause() instanceof RepositoryException) {
> +throw (RepositoryException) pe.getCause();
>  }
> +throw new RepositoryException(pe);
>  }
> +
>  changes.add(Modification.onDeleted(resource.getPath()));
>  }
>  {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Authentication Service 1.3.14

[Antonio Sanso]

+1
On Apr 6, 2016, at 2:52 PM, Antonio Sanso  wrote:

> Hi,
> 
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333896
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1451
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1451 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This majority vote is open for at least 72 hours.

[jira] [Comment Edited] (SLING-5640) add import distribution events

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229842#comment-15229842
 ] 

Nicolas Peltier edited comment on SLING-5640 at 4/7/16 7:36 AM:


thx [~mpetria]! closing, even if just for the sake of knitpicking, i could just 
change that bug into a documentation bug ;-)


was (Author: npeltier):
thx [~mpetria]! closing, even if for knitpick, i could just change that bug 
into a documentation bug ;-)

> add import distribution events
> --
>
> Key: SLING-5640
> URL: https://issues.apache.org/jira/browse/SLING-5640
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Reporter: Nicolas Peltier
>
> in order to handle distribution import, it would be handy to have a 
> distribution topic to listen to, ideally with the list of paths changed, or 
> at least the filters. i guess this should be added to the package importers ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5640) add import distribution events

[Nicolas Peltier (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Peltier resolved SLING-5640.

Resolution: Not A Bug

thx [~mpetria]! closing, even if for knitpick, i could just change that bug 
into a documentation bug ;-)

> add import distribution events
> --
>
> Key: SLING-5640
> URL: https://issues.apache.org/jira/browse/SLING-5640
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Reporter: Nicolas Peltier
>
> in order to handle distribution import, it would be handy to have a 
> distribution topic to listen to, ideally with the list of paths changed, or 
> at least the filters. i guess this should be added to the package importers ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5640) add import distribution events

[Marius Petria (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229829#comment-15229829
 ] 

Marius Petria commented on SLING-5640:
--

Events are triggered in different phases of the distribution flow [1]. I 
understand that you want to listen for 
{{DistributionEventTopics.IMPORTER_PACKAGE_IMPORTED}}.


[1] 
https://github.com/apache/sling/tree/trunk/contrib/extensions/distribution/api/src/main/java/org/apache/sling/distribution/event
[2] 
https://github.com/apache/sling/blob/trunk/contrib/extensions/distribution/api/src/main/java/org/apache/sling/distribution/event/DistributionEventTopics.java#L50

> add import distribution events
> --
>
> Key: SLING-5640
> URL: https://issues.apache.org/jira/browse/SLING-5640
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Reporter: Nicolas Peltier
>
> in order to handle distribution import, it would be handy to have a 
> distribution topic to listen to, ideally with the list of paths changed, or 
> at least the filters. i guess this should be added to the package importers ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Java 8 for launchpad?

[Carsten Ziegeler]

Hi,

the latest Apache Felix Http Jetty release is embedding latest Jetty
version which requires Java 8.

The question is now, do we want to update to that version? And if we do
so are we fine with using Java as the base for launchpad and then
ultimately for our users?

If we're not fine with Java 8 I think we have to ask the Felix project
to provide us a Java 7 based release with a Jetty version running on
Java 7 (which exists)

Staying with the http jetty version we have is no option as this means
we get no bug fixes / improvements

WDYT?


Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org