[jira] [Updated] (SLING-2660) [Tooling] Add a Sling project nature to control projects being synchronized

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-2660:
---

Summary: [Tooling] Add a Sling project nature to control projects being 
synchronized  (was: Add a Sling project nature to control projects being 
synchronized)

> [Tooling] Add a Sling project nature to control projects being synchronized
> ---
>
> Key: SLING-2660
> URL: https://issues.apache.org/jira/browse/SLING-2660
> Project: Sling
>  Issue Type: Sub-task
>  Components: Extensions
>Reporter: Robert Munteanu
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> From a usability point of view it's better to have a Sling project nature 
> which allows users to opt-in to their resources being synchronized and also 
> could allow defining repositories per project, as opposed to global projects.
> I'll try and look into this in the coming days.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2653) [Tooling] Slingclipse import wizard should use the Eclipse APIs to create resources

[Antonio Sanso (JIRA)]

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

Antonio Sanso resolved SLING-2653.
--

Resolution: Fixed

> [Tooling] Slingclipse import wizard should use the Eclipse APIs to create 
> resources
> ---
>
> Key: SLING-2653
> URL: https://issues.apache.org/jira/browse/SLING-2653
> Project: Sling
>  Issue Type: Sub-task
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Attachments: SLING-2653.diff, SLING-2653.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Since the ImportWizard use the java.io. APIs to create files and directories 
> these are not known to Eclipse and require a manual refresh. 
> This also means that the disabling of automatic sync during import does not 
> have any efect, since when I manually refresh the folder to see the results 
> the recently created resources will be re-imported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2653) [Tooling] Slingclipse import wizard should use the Eclipse APIs to create resources

[Antonio Sanso (JIRA)]

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

Antonio Sanso commented on SLING-2653:
--

Thanks for your patch Robert.
I have applied it in rev. 1408397

> [Tooling] Slingclipse import wizard should use the Eclipse APIs to create 
> resources
> ---
>
> Key: SLING-2653
> URL: https://issues.apache.org/jira/browse/SLING-2653
> Project: Sling
>  Issue Type: Sub-task
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Attachments: SLING-2653.diff, SLING-2653.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Since the ImportWizard use the java.io. APIs to create files and directories 
> these are not known to Eclipse and require a manual refresh. 
> This also means that the disabling of automatic sync during import does not 
> have any efect, since when I manually refresh the folder to see the results 
> the recently created resources will be re-imported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (SLING-2653) [Tooling] Slingclipse import wizard should use the Eclipse APIs to create resources

[Antonio Sanso (JIRA)]

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

Antonio Sanso reassigned SLING-2653:


Assignee: Antonio Sanso

> [Tooling] Slingclipse import wizard should use the Eclipse APIs to create 
> resources
> ---
>
> Key: SLING-2653
> URL: https://issues.apache.org/jira/browse/SLING-2653
> Project: Sling
>  Issue Type: Sub-task
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Attachments: SLING-2653.diff, SLING-2653.diff
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Since the ImportWizard use the java.io. APIs to create files and directories 
> these are not known to Eclipse and require a manual refresh. 
> This also means that the disabling of automatic sync during import does not 
> have any efect, since when I manually refresh the folder to see the results 
> the recently created resources will be re-imported.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to stable : sling-trunk-1.6 #1506

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-1245) Add pax runner support to maven-launchpad-plugin

[Alexandre COLLIGNON (JIRA)]

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

Alexandre COLLIGNON commented on SLING-1245:


Hi [~justinedelson] , does the attached patch look good to you ?

cheers,

Alex

> Add pax runner support to maven-launchpad-plugin
> 
>
> Key: SLING-1245
> URL: https://issues.apache.org/jira/browse/SLING-1245
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Reporter: Justin Edelson
>Priority: Minor
> Attachments: 
> 0001-SLING-1245-Add-Pax-Runner-support-for-mvn-launchpad-.patch
>
>
> In addition to the Karaf descriptor, it would be nice to output a Pax Runner 
> file as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2660) Add a Sling project nature to control projects being synchronized

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2660:
--

 Summary: Add a Sling project nature to control projects being 
synchronized
 Key: SLING-2660
 URL: https://issues.apache.org/jira/browse/SLING-2660
 Project: Sling
  Issue Type: Sub-task
  Components: Extensions
Reporter: Robert Munteanu


>From a usability point of view it's better to have a Sling project nature 
>which allows users to opt-in to their resources being synchronized and also 
>could allow defining repositories per project, as opposed to global projects.

I'll try and look into this in the coming days.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[slingclipse] Checking out resources fails if the DefaultGetServlet does not serve the content

[Robert Munteanu]

Hi,

By trying out Slingclipse on a larger project I found out that checking out a 
resource fails if the DefaultGetServlet does not serve calls for a specific 
resource, e.g.

- content ( nt:folder ) 
\- child ( my:resource )

where my:resource is served by a servlet which returns 404 on JSON calls. The 
importer correctly discovers that /content/child exists since it is listed at 
/content.1.json but then retrieval fails for /content/child.json .

What would be the best approach to handle this scenario?

Thanks,

Robert

[jira] [Resolved] (SLING-2659) System Fragment Installation should not call update on the framework

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-2659.
-

Resolution: Fixed

Fixed

> System Fragment Installation should not call update on the framework
> 
>
> Key: SLING-2659
> URL: https://issues.apache.org/jira/browse/SLING-2659
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Affects Versions: Installer Core 3.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.4.2
>
>
> If a fragment for the system bundle is installed (or updated) this should not 
> call update() on the system bundle.
> Instead for a first install it should just do nothing as it gets resolved by 
> the framework and for updates refresh on the system bundle should be called.
> (Before 3.4.0 there was a bug in system fragments handling which didn't cause 
> any action after install/update)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2659) System Fragment Installation should not call update on the framework

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2659:
---

 Summary: System Fragment Installation should not call update on 
the framework
 Key: SLING-2659
 URL: https://issues.apache.org/jira/browse/SLING-2659
 Project: Sling
  Issue Type: Bug
  Components: Installer
Affects Versions: Installer Core 3.4.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Installer Core 3.4.2


If a fragment for the system bundle is installed (or updated) this should not 
call update() on the system bundle.
Instead for a first install it should just do nothing as it gets resolved by 
the framework and for updates refresh on the system bundle should be called.
(Before 3.4.0 there was a bug in system fragments handling which didn't cause 
any action after install/update)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build became unstable: sling-trunk-1.6 #1505

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.5 » Apache Sling Integration Tests #1854

[Apache Jenkins Server]

See 


Changes:

[cziegeler] Set dependencies to latest snapshots after release

--
projectStarted 
org.apache.sling:org.apache.sling.launchpad.integration-tests:1.0.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Building Apache Sling Integration Tests 1.0.1-SNAPSHOT
[INFO] 
mojoStarted 
org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean)[INFO] Deleting 


[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean)
mojoStarted org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java)
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java)
mojoStarted org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default)
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded 
org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)[INFO] 
Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 75 resources

[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
org.apache.sling.launchpad.integration-tests ---
[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)
mojoStarted org.apache.maven.plugins:maven-antrun-plugin:1.6(default)[INFO] 
Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks

[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded org.apache.maven.plugins:maven-antrun-plugin:1.6(default)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
org.apache.sling.launchpad.integration-tests ---
[INFO] Compiling 113 source files to 

[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.5.0_22). Please file a bug at the 
Java Developer Connection (http://java.sun.com/webapps/bugreport)  after 
checking the Bug Parade for duplicates. Include your program and the following 
diagnostic in your report.  Thank you.
com.sun.tools.javac.code.Symbol$CompletionFailure: file 
org/apache/sling/adapter/annotations/Adaptable.class not found

[INFO] 1 error
[INFO] -
mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
projectFailed 
org.apache.sling:org.apache.sling.launchpad.integration-tests:1.0.1-SNAPSHOT

[jira] [Commented] (SLING-2656) Multitenancy support

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-2656:


Note that IIUC this is based on the thoughts at 
https://cwiki.apache.org/SLING/multitenancy-support.html

> Multitenancy support
> 
>
> Key: SLING-2656
> URL: https://issues.apache.org/jira/browse/SLING-2656
> Project: Sling
>  Issue Type: New Feature
>  Components: API, JCR
>Reporter: Amit Gupta
>Assignee: Felix Meschberger
> Fix For: Tenant 1.0
>
> Attachments: org.apache.sling.tenant-0.0.1-SNAPSHOT-src.zip
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Adding support for proposal listed at
> https://cwiki.apache.org/SLING/multitenancy-support.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2658) Document that the bundle list does not allow selection fo the HttpService provider

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2658:
--

 Summary: Document that the bundle list does not allow selection fo 
the HttpService provider
 Key: SLING-2658
 URL: https://issues.apache.org/jira/browse/SLING-2658
 Project: Sling
  Issue Type: Improvement
  Components: Documentation
Reporter: Robert Munteanu
Priority: Minor


At http://sling.apache.org/site/maven-launchpad-plugin.html , in the 'Bundle 
List Files' section it would be beneficial to have the following information, 
perhaps better phrased

bq. Note that the Http Service support can not be configured using the bundle 
list, but only using the jarWebSupport parameter, since it is specific to 
whether the Sling Launchpad is built as a Java Application (in which case the 
Jetty based Http Service is used) or a Web Application (in which case the Http 
Service bridge is used).

Mailing list reference: http://sling.markmail.org/thread/qireepu67eiitp23

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2657) Unable to set context path with launchpad jar

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2657:


I failed to mention that I'm using the http jetty bundle 2.2.1-SNAPSHOT ( 
r1407407 ) so I expected that to work. In the Felix Web console the 
configuration with PID org.apache.felix.http has a 'context path' property set 
to '/' , even though I started the launchpad with -r /ctx .

As a matter of fact, even if I set the context path to '/ctx' and restart Sling 
it still use the root context path.

> Unable to set context path with launchpad jar
> -
>
> Key: SLING-2657
> URL: https://issues.apache.org/jira/browse/SLING-2657
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Base 2.4.0
>Reporter: Robert Munteanu
> Attachments: contextpath.zip
>
>
> When building a launchpad jar and configuring it to use the http jetty bundle 
> as of revision 1407407 the -r parameter does not cause the context path to be 
> set.
> When launching the launchpad jar with 
> java -jar target/contextpath-0.0.SNAPSHOT.jar -r /ctx
> I get the following log output
> 11.11.2012 15:04:45.265 *INFO * [main] Setting sling.home=sling (default)
> 11.11.2012 15:04:45.266 *INFO * [main] Starting Apache Sling in 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.276 *INFO * [main] Checking launcher JAR in folder 
> /mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.289 *INFO * [main] Existing launcher is up to date, using 
> it: 2.4.0 (org.apache.sling.launchpad.base.jar)
> 11.11.2012 15:04:45.291 *INFO * [main] Loading launcher class 
> org.apache.sling.launchpad.base.app.MainDelegate from 
> org.apache.sling.launchpad.base.jar
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> sling.launchpad=/mnt/md/robert/workspace/contextpath/sling
> 11.11.2012 15:04:45.307 *INFO * [main] Setting 
> org.apache.felix.http.context_path=/ctx
> 11.11.2012 15:04:45.307 *INFO * [main] Starting launcher ...
> 11.11.2012 15:04:45.309 *INFO * [main] HTTP server port: 8080
> SLF4J: The following loggers will not work becasue they were created
> SLF4J: during the default configuration phase of the underlying logging 
> system.
> SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
> SLF4J: org.apache.sling.commons.log.internal.LogServiceFactory
> 2012-11-11 15:04:46.079:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.131:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.368:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 2012-11-11 15:04:46.467:INFO:oejsh.ContextHandler:stopped 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.520:INFO:oejs.Server:jetty-7.x.y-SNAPSHOT
> 2012-11-11 15:04:46.520:INFO:oejsh.ContextHandler:started 
> o.e.j.s.ServletContextHandler{/,null}
> 2012-11-11 15:04:46.560:INFO:oejs.AbstractConnector:Started 
> SelectChannelConnector@0.0.0.0:8080
> 11.11.2012 15:04:53.357 *INFO * [main] Startup completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.5 » Apache Sling Integration Tests #1853

[Apache Jenkins Server]

See 


--
projectStarted 
org.apache.sling:org.apache.sling.launchpad.integration-tests:1.0.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] Building Apache Sling Integration Tests 1.0.1-SNAPSHOT
[INFO] 
mojoStarted 
org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean)[INFO] Deleting 


[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded org.apache.maven.plugins:maven-clean-plugin:2.4.1(default-clean)
mojoStarted org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java)
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded org.apache.maven.plugins:maven-enforcer-plugin:1.0(enforce-java)
mojoStarted org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default)
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ 
org.apache.sling.launchpad.integration-tests ---
mojoSucceeded 
org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default)
mojoStarted 
org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)[INFO] 
Using 'UTF-8' encoding to copy filtered resources.

[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
org.apache.sling.launchpad.integration-tests ---
[INFO] Copying 75 resources
[INFO] Copying 3 resources
mojoSucceeded 
org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)
mojoStarted org.apache.maven.plugins:maven-antrun-plugin:1.6(default)
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run (default) @ 
org.apache.sling.launchpad.integration-tests ---
[INFO] Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks
mojoSucceeded org.apache.maven.plugins:maven-antrun-plugin:1.6(default)
mojoStarted 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
org.apache.sling.launchpad.integration-tests ---
[INFO] Compiling 113 source files to 

[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.5.0_22). Please file a bug at the 
Java Developer Connection (http://java.sun.com/webapps/bugreport)  after 
checking the Bug Parade for duplicates. Include your program and the following 
diagnostic in your report.  Thank you.
com.sun.tools.javac.code.Symbol$CompletionFailure: file 
org/apache/sling/adapter/annotations/Adaptable.class not found

[INFO] 1 error
[INFO] -
mojoFailed org.apache.maven.plugins:maven-compiler-plugin:2.5.1(default-compile)
projectFailed 
org.apache.sling:org.apache.sling.launchpad.integration-tests:1.0.1-SNAPSHOT

[jira] [Resolved] (SLING-2656) Multitenancy support

[Felix Meschberger (JIRA)]

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

Felix Meschberger resolved SLING-2656.
--

   Resolution: Fixed
Fix Version/s: Tenant 1.0

I think this can be resolved for now.

> Multitenancy support
> 
>
> Key: SLING-2656
> URL: https://issues.apache.org/jira/browse/SLING-2656
> Project: Sling
>  Issue Type: New Feature
>  Components: API, JCR
>Reporter: Amit Gupta
>Assignee: Felix Meschberger
> Fix For: Tenant 1.0
>
> Attachments: org.apache.sling.tenant-0.0.1-SNAPSHOT-src.zip
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Adding support for proposal listed at
> https://cwiki.apache.org/SLING/multitenancy-support.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2656) Multitenancy support

[Felix Meschberger (JIRA)]

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

Felix Meschberger updated SLING-2656:
-

Affects Version/s: (was: API 2.2.4)

> Multitenancy support
> 
>
> Key: SLING-2656
> URL: https://issues.apache.org/jira/browse/SLING-2656
> Project: Sling
>  Issue Type: New Feature
>  Components: API, JCR
>Reporter: Amit Gupta
>Assignee: Felix Meschberger
> Attachments: org.apache.sling.tenant-0.0.1-SNAPSHOT-src.zip
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Adding support for proposal listed at
> https://cwiki.apache.org/SLING/multitenancy-support.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-2529:


Fix Version/s: (was: JCR Resource 2.2.0)
   JCR Resource 2.2.2

> Add support for JCR Observation event types: NODE_MOVED and PERSIST
> ---
>
> Key: SLING-2529
> URL: https://issues.apache.org/jira/browse/SLING-2529
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Resource 2.1.0
>Reporter: Felix Meschberger
>Assignee: Felix Meschberger
> Fix For: JCR Resource 2.2.2
>
>
> The JcrResourceListener does not currently support two event types added in 
> the JCR 2.0 specification:
>   * NODE_MOVED
>   * PERSIST
> Particularly NODE_MOVED is an important event which we should support with a 
> properly mapped OSGi event.
> The PERSIST event might be useful in creating event group boundaries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-2529:
-

Moving this to the next release

> Add support for JCR Observation event types: NODE_MOVED and PERSIST
> ---
>
> Key: SLING-2529
> URL: https://issues.apache.org/jira/browse/SLING-2529
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Resource 2.1.0
>Reporter: Felix Meschberger
>Assignee: Felix Meschberger
> Fix For: JCR Resource 2.2.2
>
>
> The JcrResourceListener does not currently support two event types added in 
> the JCR 2.0 specification:
>   * NODE_MOVED
>   * PERSIST
> Particularly NODE_MOVED is an important event which we should support with a 
> properly mapped OSGi event.
> The PERSIST event might be useful in creating event group boundaries.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2320) Current DOS-prevention for infinity.json can prevent enumeration of children

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-2320.
-

Resolution: Fixed

> Current DOS-prevention for infinity.json can prevent enumeration of children
> 
>
> Key: SLING-2320
> URL: https://issues.apache.org/jira/browse/SLING-2320
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.0
>Reporter: Jeff Young
>Assignee: Felix Meschberger
>  Labels: newbie, patch
> Fix For: Servlets Get 2.1.4
>
> Attachments: json_get_servlet_rewrite.patch, jsonRenderer.diff, 
> servlets-get.patch, servlet_tests.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> A request of resource.1.json should always succeed, as it's the primary 
> method for JSON introspection of the repository hierarchy.  DOS protection 
> should only apply to "deep" traversals; that is, anything with a depth 
> greater than 1 (and, in particular, resource.infinity.json).
> For a fuller discussion, see: 
> http://www.mail-archive.com/dev@sling.apache.org/msg13961.html.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira