date:20160219

[jira] [Updated] (SLING-4558) Simpler serviceuser config for service user mappings

2016-02-19 Thread Alexander Klimetschek (JIRA)


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

Alexander Klimetschek updated SLING-4558:
-
Issue Type: Improvement  (was: Bug)

> Simpler serviceuser config for service user mappings
> 
>
> Key: SLING-4558
> URL: https://issues.apache.org/jira/browse/SLING-4558
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Reporter: Alexander Klimetschek
> Attachments: SLING-4558.patch
>
>
> For a service user configuration (amendment), one has to currently remember a 
> weird long PID:
> {{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
> plus making sure it has a unique ID by appending {{-something}}, which 
> confuses people as to whether that "something" must correspond to a bundle or 
> service name (not necessary) or they come up with these long names:
> {{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
> which then create too long paths for some cases (git checkouts under windows 
> or jcr repository limitations).
> A simple {{serviceuser}} config node name would be better.
> For reference, the target service is 
> [MappingConfigAmendment|https://github.com/apache/sling/blob/trunk/bundles/extensions/serviceusermapper/src/main/java/org/apache/sling/serviceusermapping/impl/MappingConfigAmendment.java]



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

[ide] Adding a m2e project configurator for the 'content-package' packaging type

2016-02-19 Thread Robert Munteanu

Hi,

We have a patch contributed some time ago in SLING-3100 [1] which adds
a m2e configurator for the content-package packaging type.

What this means is that when a Maven project which is of type 'content-
package' is imported into Eclipse it's automatically configured as a
Sling content project, which removes a lot of frustration when users
import a project and it simply does not work :-)

My first reaction at that time was to put the patch on hold, since the
content-package packaging type is contributed by the
com.day.jcr.vault:content-package-maven-plugin, which is not open
source.

Thinking about this two years later, I am not sure whether that was
justified, since (1) the patch does not link to any kind of code which
is not Apache-2.0 friendly, but just makes a metadata entry related to
that plugin.

Also, (2) this would help a lot users that use the IDE tooling together
with the content-package-maven-plugin.

Keeping (1) in mind, is it acceptable from a legal POV to include this
patch?

Thanks,

Robert


[1]: https://issues.apache.org/jira/browse/SLING-3100

[jira] [Commented] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

2016-02-19 Thread Konrad Windszus (JIRA)


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

Konrad Windszus commented on SLING-5227:


I doubt that using the {{getThreadResourceResolver}} will work at all in that 
context, because this request is not being handled by Sling itself (because it 
is the Felix Webconsole). 
[~cziegeler] Are you sure that in this case the thread local contains a 
resource resolver for Sling? I know that usually Sling is used as Security 
Provider [1], but I am not sure this is really enough here.


[1] - 
https://sling.apache.org/documentation/bundles/web-console-extensions.html 

> Remove loginAdministrative() usage from org.apache.sling.bgservlets
> ---
>
> Key: SLING-5227
> URL: https://issues.apache.org/jira/browse/SLING-5227
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Antonio Sanso
>Assignee: Bertrand Delacretaz
>
> Counted 1 occurrence



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

[jira] [Comment Edited] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

2016-02-19 Thread Alexandre COLLIGNON (JIRA)


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

Alexandre COLLIGNON edited comment on SLING-5227 at 2/19/16 4:30 PM:
-

Nice. I will try that. Are you aware of a smart/short way to retrieve a 
reference of the factory? I can go the full OSGi BundleContext and 
ServiceReference way... but I prefer to ask first :D.


was (Author: acollign):
Nice. I will try that. 

> Remove loginAdministrative() usage from org.apache.sling.bgservlets
> ---
>
> Key: SLING-5227
> URL: https://issues.apache.org/jira/browse/SLING-5227
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Antonio Sanso
>Assignee: Bertrand Delacretaz
>
> Counted 1 occurrence



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

[jira] [Commented] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

2016-02-19 Thread Alexandre COLLIGNON (JIRA)


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

Alexandre COLLIGNON commented on SLING-5227:


Nice. I will try that. 

> Remove loginAdministrative() usage from org.apache.sling.bgservlets
> ---
>
> Key: SLING-5227
> URL: https://issues.apache.org/jira/browse/SLING-5227
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Antonio Sanso
>Assignee: Bertrand Delacretaz
>
> Counted 1 occurrence



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

[jira] [Commented] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Alexandre COLLIGNON (JIRA)


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

Alexandre COLLIGNON commented on SLING-5535:


Thank you [~bdelacretaz]!

> Background Job Web Console should use POST for job manipulation
> ---
>
> Key: SLING-5535
> URL: https://issues.apache.org/jira/browse/SLING-5535
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Alexandre COLLIGNON
>Assignee: Bertrand Delacretaz
> Fix For: Background Servlets 1.0.4
>
> Attachments: SLING-5535.patch
>
>
> At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP 
> Get. It would nicer to perform such job manipulation on Post only.



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

[jira] [Resolved] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Bertrand Delacretaz (JIRA)


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

Bertrand Delacretaz resolved SLING-5535.

Resolution: Fixed

I have applied your patch in revision 1731256, thanks!

> Background Job Web Console should use POST for job manipulation
> ---
>
> Key: SLING-5535
> URL: https://issues.apache.org/jira/browse/SLING-5535
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Alexandre COLLIGNON
>Assignee: Bertrand Delacretaz
> Fix For: Background Servlets 1.0.4
>
> Attachments: SLING-5535.patch
>
>
> At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP 
> Get. It would nicer to perform such job manipulation on Post only.



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

[jira] [Updated] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Bertrand Delacretaz (JIRA)


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

Bertrand Delacretaz updated SLING-5535:
---
Fix Version/s: Background Servlets 1.0.4

> Background Job Web Console should use POST for job manipulation
> ---
>
> Key: SLING-5535
> URL: https://issues.apache.org/jira/browse/SLING-5535
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Alexandre COLLIGNON
>Assignee: Bertrand Delacretaz
> Fix For: Background Servlets 1.0.4
>
> Attachments: SLING-5535.patch
>
>
> At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP 
> Get. It would nicer to perform such job manipulation on Post only.



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

[jira] [Updated] (SLING-5536) Add integration test for binaryless distribution

2016-02-19 Thread Andrei Dulceanu (JIRA)


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

Andrei Dulceanu updated SLING-5536:
---
Attachment: binaryless-test.patch

> Add integration test for binaryless distribution
> 
>
> Key: SLING-5536
> URL: https://issues.apache.org/jira/browse/SLING-5536
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution, Testing
>Reporter: Andrei Dulceanu
> Attachments: binaryless-test.patch
>
>
> Add integration test for binaryless distribution



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

[jira] [Commented] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler commented on SLING-5227:
-

The ResourceResolverFactory#getThreadResourceResolver can be used to get the 
Resource Resolver of the current user

> Remove loginAdministrative() usage from org.apache.sling.bgservlets
> ---
>
> Key: SLING-5227
> URL: https://issues.apache.org/jira/browse/SLING-5227
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Antonio Sanso
>Assignee: Bertrand Delacretaz
>
> Counted 1 occurrence



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

[jira] [Created] (SLING-5536) Add integration test for binaryless distribution

2016-02-19 Thread Andrei Dulceanu (JIRA)

Andrei Dulceanu created SLING-5536:
--

 Summary: Add integration test for binaryless distribution
 Key: SLING-5536
 URL: https://issues.apache.org/jira/browse/SLING-5536
 Project: Sling
  Issue Type: Improvement
  Components: Distribution, Testing
Reporter: Andrei Dulceanu


Add integration test for binaryless distribution



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

[jira] [Assigned] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Bertrand Delacretaz (JIRA)


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

Bertrand Delacretaz reassigned SLING-5535:
--

Assignee: Bertrand Delacretaz

Oops, did I really write that code? It looks like I did ;-)

I'll have a look later today.

> Background Job Web Console should use POST for job manipulation
> ---
>
> Key: SLING-5535
> URL: https://issues.apache.org/jira/browse/SLING-5535
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Alexandre COLLIGNON
>Assignee: Bertrand Delacretaz
> Attachments: SLING-5535.patch
>
>
> At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP 
> Get. It would nicer to perform such job manipulation on Post only.



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

[jira] [Commented] (SLING-5227) Remove loginAdministrative() usage from org.apache.sling.bgservlets

2016-02-19 Thread Alexandre COLLIGNON (JIRA)


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

Alexandre COLLIGNON commented on SLING-5227:


As far as I can tell, the only occurrence of loginAdmin is in the WebConsole 
Plugin [1]. Assuming that only administrators have access to the web console, 
it is fair to assume that whoever renders jobs will have access to the 
underlying content.

I would therefore recommend to use the user session to perform job manipulation.

[1] {{JobConsolePlugin.Plugin#renderContent}}

> Remove loginAdministrative() usage from org.apache.sling.bgservlets
> ---
>
> Key: SLING-5227
> URL: https://issues.apache.org/jira/browse/SLING-5227
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Antonio Sanso
>Assignee: Bertrand Delacretaz
>
> Counted 1 occurrence



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

[jira] [Updated] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Alexandre COLLIGNON (JIRA)


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

Alexandre COLLIGNON updated SLING-5535:
---
Attachment: SLING-5535.patch

Attaching patch. [~bdelacretaz], may I ask you to have a look?

> Background Job Web Console should use POST for job manipulation
> ---
>
> Key: SLING-5535
> URL: https://issues.apache.org/jira/browse/SLING-5535
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Alexandre COLLIGNON
> Attachments: SLING-5535.patch
>
>
> At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP 
> Get. It would nicer to perform such job manipulation on Post only.



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

[jira] [Comment Edited] (SLING-5520) Update Oak to 1.4

2016-02-19 Thread Oliver Lietz (JIRA)


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

Oliver Lietz edited comment on SLING-5520 at 2/19/16 1:34 PM:
--

update to Oak {{1.3.14}} done in [r1730319|https://svn.apache.org/r1730319]


was (Author: olli):
update to Oak {{1.3.4}} done in [r1730319|https://svn.apache.org/r1730319]

> Update Oak to 1.4
> -
>
> Key: SLING-5520
> URL: https://issues.apache.org/jira/browse/SLING-5520
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Launchpad, Oak
>Reporter: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0, JCR Oak Server 1.0.2, 
> Launchpad Builder 9
>
>
> Doing update in several more steps until Oak {{1.4}} is released due to major 
> changes, one of them being OAK-3842 (removed package exports, tracked in 
> SLING-5511).
> First updating to Oak {{1.3.14}} (latest pre OAK-3842 release) and then to 
> Oak {{1.3.15}}.
> Features deprecated for Oak {{1.4}} should be removed from 
> {{org.apache.sling.jcr.oak.server}}.



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

[jira] [Created] (SLING-5535) Background Job Web Console should use POST for job manipulation

2016-02-19 Thread Alexandre COLLIGNON (JIRA)

Alexandre COLLIGNON created SLING-5535:
--

 Summary: Background Job Web Console should use POST for job 
manipulation
 Key: SLING-5535
 URL: https://issues.apache.org/jira/browse/SLING-5535
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Background Servlets 1.0.2
Reporter: Alexandre COLLIGNON


At the moment, the {{JobConsolePlugin.Plugin}} processes commands on HTTP Get. 
It would nicer to perform such job manipulation on Post only.



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

Re: Build failed in Jenkins: sling-trunk-1.7 #3417

2016-02-19 Thread Carsten Ziegeler

Now, this really looks strange to me:


[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] No compiler is provided in this environment. Perhaps you are
running on a JRE rather than a JDK?


Carsten

Apache Jenkins Server wrote
> See 
> 
> Changes:
> 
> [sseifert] SLING-5531 Sling-Namespaces bundle header for registering JCR 
> namespaces broken
> 
> --
> [...truncated 12348 lines...]
> [INFO] Apache Sling Distributed Event Admin .. SKIPPED
> [INFO] Apache Sling Discovery API  SKIPPED
> [INFO] Apache Sling Discovery Commons  SKIPPED
> [INFO] Apache Sling Discovery Base ... SKIPPED
> [INFO] Apache Sling Resource-Based Discovery Service . SKIPPED
> [INFO] Apache Sling Oak-Based Discovery Service .. SKIPPED
> [INFO] Apache Sling Discovery Support Bundle . SKIPPED
> [INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED
> [INFO] Apache Sling Event Support  SKIPPED
> [INFO] Apache Sling Feature Flags  SKIPPED
> [INFO] Apache Sling javax.activation bundle .. SKIPPED
> [INFO] Apache Sling Service User Mapper .. SKIPPED
> [INFO] Apache Sling Settings . SKIPPED
> [INFO] Apache Sling Web Console Branding . SKIPPED
> [INFO] Apache Sling Web Console Security Provider  SKIPPED
> [INFO] Apache Sling Explorer . SKIPPED
> [INFO] Apache Sling Health Check Core  SKIPPED
> [INFO] Apache Sling Health Check Annotations . SKIPPED
> [INFO] Apache Sling Health Check Samples . SKIPPED
> [INFO] Apache Sling Health Check Support Components .. SKIPPED
> [INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED
> [INFO] Apache Sling Health Check JUnit Bridge  SKIPPED
> [INFO] Apache Sling Health Check Integration Tests ... SKIPPED
> [INFO] Apache Sling Health Check Reactor POM . SKIPPED
> [INFO] Apache Sling Resource Access Security . SKIPPED
> [INFO] Apache Sling Resource Access Security Integration Tests  SKIPPED
> [INFO] Apache Sling Validation Framework API . SKIPPED
> [INFO] Apache Sling Validation Framework Core Implementation  SKIPPED
> [INFO] Apache Sling Validation Framework Testing Services  SKIPPED
> [INFO] Apache Sling Validation Framework Integration Tests  SKIPPED
> [INFO] Apache Sling Validation Framework Examples  SKIPPED
> [INFO] Apache Sling Validation Framework Builder . SKIPPED
> [INFO] Apache Sling Models API ... SKIPPED
> [INFO] Apache Sling Models Implementation  SKIPPED
> [INFO] Apache Sling Models Validation Implementation . SKIPPED
> [INFO] Apache Sling Models Integration Tests . SKIPPED
> [INFO] Apache Sling Internationalization Support . SKIPPED
> [INFO] Apache Sling XSS Protection Bundle  SKIPPED
> [INFO] Apache Sling Resource Builder . SKIPPED
> [INFO] Apache Sling Servlet Helpers .. SKIPPED
> [INFO] Apache Sling Test Tools ... SKIPPED
> [INFO] Apache Sling Testing Hamcrest . SKIPPED
> [INFO] Apache Sling JUnit Core ... SKIPPED
> [INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
> [INFO] Apache Sling JUnit Health Checks .. SKIPPED
> [INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
> [INFO] Apache Sling JUnit Performance  SKIPPED
> [INFO] Apache Sling Testing Mock Log Configuration ... SKIPPED
> [INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
> [INFO] Apache Sling Testing JCR Mock . SKIPPED
> [INFO] Apache Sling Testing OSGi Mock  SKIPPED
> [INFO] Apache Sling Testing Sling Mock ... SKIPPED
> [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver  
> SKIPPED
> [INFO] Apache Sling Testing Mocks Modules Reactor  SKIPPED
> [INFO] Apache Sling Sample Server-Side Tests . SKIPPED
> [INFO] Apache Sling Failing Server-Side Tests  SKIPPED
> [INFO] Apache Sling Sample Integration Tests . SKIPPED
> [INFO] Apache Sling Testing - sample bundle with integration tests  SKIPPED
> [INFO] Apache Sling Testing Modules Reactor .. SKIPPED
> [INFO] Apache Sling Installer  SKIPPED
> [INFO] Apache Sling File Installer ... SKIPPED
> [INFO] Apache Sling JCR Installer  SKIPPED
> [INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
> [INFO] Apache Sling Deployment Package Installer . SKIPPED
>

[jira] [Updated] (SLING-5534) Improve namespace handling

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler updated SLING-5534:

Attachment: patch.txt

[~sseif...@pro-vision.de] This is a potential change which should apply the 
namespace immediately (I didn't remove the proxies in this patch yet). WDYT?

> Improve namespace handling
> --
>
> Key: SLING-5534
> URL: https://issues.apache.org/jira/browse/SLING-5534
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Base 2.3.2
>
> Attachments: patch.txt
>
>
> Right now the namespace handling support requries a proxy of the session 
> object (in order to have namespace handling for impersonated session).
> In addition for each new session, the mapping code is run, although it should 
> only run once and register the namespaces in the registry.
> This should improve performance as we don't have to run the namespace 
> handling code for each and every session and get rid of the proxy.
> The namespace registration itself gets a little more tricky, but basically we 
> can directly change the registry whenever a bundle with a namespace header 
> arrives. We just need to think about collition handling



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

Re: Naming a new support bundle

2016-02-19 Thread Julian Sedding

Hi

I wrote a small bundle a few years ago that exposed all bundles
installed in a Felix instance as a maven repository (provided they
contain the necessary meta data). There should be significant overlap
in the functionality. The most useful entry point is probably[0]. Feel
free to use any parts of the code as you see fit. Note that
DependencyInspector#getBundleFile(final Bundle bundle) relies on Felix
implementation details, not sure if the same can be done in a more
portable way.

Konrad wrote:
> Also I would think that such a servlet may also be useful to
> create a dependency management section within a pom [...]

The "Artifx" implementation is a webconsole plugin, exposed at
/system/console/artifx and can be used as a maven repository. In
addition it generates a pom containing all dependency information
ready to include in another pom with scope=import. Each dependency is
annotated with it's exported packages in an XML comment for
convenience. Unfortunately this pom is a bit hidden, you find it under
/system/console/artifx/local/generated-pom/{hash of dependencies}/.

Regards
Julian

[0] 
https://github.com/code-distillery/artifx/blob/master/src/main/java/net/distilledcode/artifx/impl/DependencyInspector.java

On Fri, Feb 19, 2016 at 9:13 AM, Grigore Zsolt
 wrote:
> Hi Konrad,
>
> Also I would think that such a servlet may also be useful to create a
>> dependency management section within a pom (for depending on the version of
>> the dependency which is actually used in Sling). I would prefer to have
>> that  servlet at Felix in the form of another web console.
>> Konrad
>>
>> I have something similar implemented in [0]. It is part of a small tooling
> bundle for dependency generation, although it is not a web console tab.
> Feel free to use it.
>
> Regards,
> Zsolt
>
> [0]:
> https://github.com/zsoltgrigore/sling-depgen/blob/master/src/main/java/org/konzult/sling/utils/depgen/impl/handler/POMGeneratorImpl.java

[jira] [Commented] (SLING-5534) Improve namespace handling

2016-02-19 Thread Stefan Seifert (JIRA)


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

Stefan Seifert commented on SLING-5534:
---

yes, this came to my mind as well in context of SLING-5531

> Improve namespace handling
> --
>
> Key: SLING-5534
> URL: https://issues.apache.org/jira/browse/SLING-5534
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Base 2.3.2
>
>
> Right now the namespace handling support requries a proxy of the session 
> object (in order to have namespace handling for impersonated session).
> In addition for each new session, the mapping code is run, although it should 
> only run once and register the namespaces in the registry.
> This should improve performance as we don't have to run the namespace 
> handling code for each and every session and get rid of the proxy.
> The namespace registration itself gets a little more tricky, but basically we 
> can directly change the registry whenever a bundle with a namespace header 
> arrives. We just need to think about collition handling



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

[jira] [Resolved] (SLING-5531) Sling-Namespaces bundle header for registering JCR namespaces broken

2016-02-19 Thread Stefan Seifert (JIRA)


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

Stefan Seifert resolved SLING-5531.
---
Resolution: Fixed

Completed: At revision: 1731199  


> Sling-Namespaces bundle header for registering JCR namespaces broken
> 
>
> Key: SLING-5531
> URL: https://issues.apache.org/jira/browse/SLING-5531
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Base 2.3.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Critical
> Fix For: JCR Base 2.3.2
>
> Attachments: AbstractSlingRepository2.patch
>
>
> the changes for SLING-4937 (Drop namespace mapping support) broke the 
> "Declared Node Type Registration" feature described in [1].
> this allows to register custom JCR namespaces or nodetypes via a CND file 
> when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} 
> bundle header.
> i assume only the support for {{Sling-Namespaces}} should be removed with 
> SLING-4937, not the support for {{Sling-Nodetypes}}.
> [1] 
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html



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

[jira] [Updated] (SLING-5531) Sling-Namespaces bundle header for registering JCR namespaces broken

2016-02-19 Thread Stefan Seifert (JIRA)


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

Stefan Seifert updated SLING-5531:
--
Assignee: Stefan Seifert  (was: Carsten Ziegeler)
 Summary: Sling-Namespaces bundle header for registering JCR namespaces 
broken  (was: Declared Node Type Registration support broken in JCR Base)

> Sling-Namespaces bundle header for registering JCR namespaces broken
> 
>
> Key: SLING-5531
> URL: https://issues.apache.org/jira/browse/SLING-5531
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Base 2.3.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Critical
> Fix For: JCR Base 2.3.2
>
> Attachments: AbstractSlingRepository2.patch
>
>
> the changes for SLING-4937 (Drop namespace mapping support) broke the 
> "Declared Node Type Registration" feature described in [1].
> this allows to register custom JCR namespaces or nodetypes via a CND file 
> when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} 
> bundle header.
> i assume only the support for {{Sling-Namespaces}} should be removed with 
> SLING-4937, not the support for {{Sling-Nodetypes}}.
> [1] 
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html



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

[jira] [Commented] (SLING-5531) Declared Node Type Registration support broken in JCR Base

2016-02-19 Thread Stefan Seifert (JIRA)


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

Stefan Seifert commented on SLING-5531:
---

just tested this again - yes nodetype registration was working with 2.3.0. root 
case for the wrong testcase initially was that restarting the jcr.base bundle 
itself has not effect and does not lead to re-checking deployed bundle headers 
- because it contains only abstract classes, and they are only reloaded if the 
consuming bundle like oak-server are restarted.

will update the ticket title and apply the patch.

> Declared Node Type Registration support broken in JCR Base
> --
>
> Key: SLING-5531
> URL: https://issues.apache.org/jira/browse/SLING-5531
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Base 2.3.0
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
>Priority: Critical
> Fix For: JCR Base 2.3.2
>
> Attachments: AbstractSlingRepository2.patch
>
>
> the changes for SLING-4937 (Drop namespace mapping support) broke the 
> "Declared Node Type Registration" feature described in [1].
> this allows to register custom JCR namespaces or nodetypes via a CND file 
> when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} 
> bundle header.
> i assume only the support for {{Sling-Namespaces}} should be removed with 
> SLING-4937, not the support for {{Sling-Nodetypes}}.
> [1] 
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html



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

[jira] [Commented] (SLING-5531) Declared Node Type Registration support broken in JCR Base

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler commented on SLING-5531:
-

[~sseif...@pro-vision.de] Is it correct that the node type support is not 
broking, but just namespace handling? The Loader should handle nodetype 
registrations directly

> Declared Node Type Registration support broken in JCR Base
> --
>
> Key: SLING-5531
> URL: https://issues.apache.org/jira/browse/SLING-5531
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Base 2.3.0
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
>Priority: Critical
> Fix For: JCR Base 2.3.2
>
> Attachments: AbstractSlingRepository2.patch
>
>
> the changes for SLING-4937 (Drop namespace mapping support) broke the 
> "Declared Node Type Registration" feature described in [1].
> this allows to register custom JCR namespaces or nodetypes via a CND file 
> when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} 
> bundle header.
> i assume only the support for {{Sling-Namespaces}} should be removed with 
> SLING-4937, not the support for {{Sling-Nodetypes}}.
> [1] 
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html



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

Re: Naming a new support bundle

2016-02-19 Thread Grigore Zsolt

Hi Konrad,

Also I would think that such a servlet may also be useful to create a
> dependency management section within a pom (for depending on the version of
> the dependency which is actually used in Sling). I would prefer to have
> that  servlet at Felix in the form of another web console.
> Konrad
>
> I have something similar implemented in [0]. It is part of a small tooling
bundle for dependency generation, although it is not a web console tab.
Feel free to use it.

Regards,
Zsolt

[0]:
https://github.com/zsoltgrigore/sling-depgen/blob/master/src/main/java/org/konzult/sling/utils/depgen/impl/handler/POMGeneratorImpl.java

[jira] [Closed] (SLING-5513) Deprecate JcrResourceUtil

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5513.
---

> Deprecate JcrResourceUtil
> -
>
> Key: SLING-5513
> URL: https://issues.apache.org/jira/browse/SLING-5513
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Affects Versions: JCR Resource 2.7.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.7.2
>
>
> I think we should deprecate the jcr resource API completely, most of it
> is already deprecated. Deprecating will allow us to get rid of it in the
> future and reduce the parts we have to maintain.
> Most of that API is very old and was created in a time where we didn't
> have CRUD support for resources. Now that we have this for some time,
> there shouldn't be a need for any of this API. And if so, jackrabbit
> would be a much better place.
> Right now, we still have not deprecated:
> JcrResourceUtil#query - Resource Resolver should be used instead.
> JcrResourceUtil#toJavaObject - Value Map should be used instead.
> JcrResourceUtil#createValue - Modifiable Value Map should be used instead.
> JcrResourceUtil#setProperty - Modifiable Value Map should be used instead.
> JcrResourceUtil#createPath - ResourceUtil#getOrCreateResource should be
> used instead
> This leaves us with some constants in JcrResourceConstants. Although I
> would love to get rid of them to not have any API at all in the jcr
> resource bundle, some of them are really related to the jcr resource
> provider.



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

[jira] [Closed] (SLING-5499) Servlets resource provider is hiding resources from other providers

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5499.
---

> Servlets resource provider is hiding resources from other providers
> ---
>
> Key: SLING-5499
> URL: https://issues.apache.org/jira/browse/SLING-5499
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.4.2
>
>
> The new servlet resource provider implementation is based on the new resource 
> provider API. For example if a servlet is mounted at the path (!) /libs/foo, 
> all resources underneath this resource, like /libs/foo/bla are tried with the 
> servlet resource provider.
> The old implementation of the resource resolver switched to the resource 
> provider at / and tried it there
> This is a change of behaviour and we should revert to the old behaviour



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

[jira] [Closed] (SLING-5500) ResourceResolver#remove(Resource) fails on JcrResource that is a Property

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5500.
---

> ResourceResolver#remove(Resource) fails on JcrResource that is a Property
> -
>
> Key: SLING-5500
> URL: https://issues.apache.org/jira/browse/SLING-5500
> Project: Sling
>  Issue Type: Bug
>  Components: JCR, ResourceResolver
>Affects Versions: JCR Resource 2.7.0
>Reporter: Christan Keller
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.7.2
>
>
> Let Path point to a Property in a JCR Repository
> {code}
> Resource toDelete = resourceResolver.getResource(path);
> if (toDelete != null) {
>  resourceResolver.delete(toDelete);
> }
> {code}
> Ends in a PathNotFoundException. 
> Seems to be introduced by SLING-5491 found in Bundle Version 2.7.1.R1728839



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

[jira] [Closed] (SLING-5506) JcrResourceProvider must be stateless

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5506.
---

> JcrResourceProvider must be stateless
> -
>
> Key: SLING-5506
> URL: https://issues.apache.org/jira/browse/SLING-5506
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Resource 2.7.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.7.2
>
>
> With the refactoring of the JcrResourceProvider, the provider became 
> stateless. Unfortunately not all stateful data has been moved into the new 
> context object.



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

[jira] [Closed] (SLING-5491) JcrResourceProvider#delete should not cast Resource to JcrItemResource

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5491.
---

> JcrResourceProvider#delete should not cast Resource to JcrItemResource
> --
>
> Key: SLING-5491
> URL: https://issues.apache.org/jira/browse/SLING-5491
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Resource 2.7.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.7.2
>
>
> The code at
> https://github.com/apache/sling/blob/f4751528432eca4e54e3161d501b43b605f92ae7/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrResourceProvider.java#l440
> is directly casting to a JcrItemResource - if e.g. a wrapped resource is 
> passed in, this fails



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

[jira] [Closed] (SLING-5498) ResolveContext#getParentResourceProvider always returns null

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5498.
---

> ResolveContext#getParentResourceProvider always returns null
> 
>
> Key: SLING-5498
> URL: https://issues.apache.org/jira/browse/SLING-5498
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>




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

[jira] [Closed] (SLING-5503) ConcurrentModificationException while iterating over existing providers

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5503.
---

> ConcurrentModificationException while iterating over existing providers
> ---
>
> Key: SLING-5503
> URL: https://issues.apache.org/jira/browse/SLING-5503
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> Some methods in ResourceResolverControl iterate over the current set of used 
> providers. However, if while iterating this list is modified, the set is 
> modified the following exception occurs:
> java.util.ConcurrentModificationException: null
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859)
> at java.util.ArrayList$Itr.next(ArrayList.java:831)
> at 
> org.apache.sling.resourceresolver.impl.helper.ResourceResolverControl.commit(ResourceResolverControl.java:405)
> at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.commit(ResourceResolverImpl.java:1218)



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

[jira] [Closed] (SLING-5496) Adaptable is not implemented for legacy providers

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5496.
---

> Adaptable is not implemented for legacy providers
> -
>
> Key: SLING-5496
> URL: https://issues.apache.org/jira/browse/SLING-5496
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> If a legacy provider implements Adaptable, adaptTo is never called



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

[jira] [Closed] (SLING-5510) Resource resolver should always use most current set of providers

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5510.
---

> Resource resolver should always use most current set of providers
> -
>
> Key: SLING-5510
> URL: https://issues.apache.org/jira/browse/SLING-5510
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> Currently, the resource resolver gets the set of providers at the time of 
> creation of the resolver. Especially with long running resolvers which are 
> created "early" , this means that they don't see providers which were 
> registered after the resolver was created.



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

[jira] [Closed] (SLING-5509) Behaviour Change in Resource#getParent

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5509.
---

> Behaviour Change in Resource#getParent
> --
>
> Key: SLING-5509
> URL: https://issues.apache.org/jira/browse/SLING-5509
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> In versions pre 1.4.0 it was possible to call getParent on a resource with a 
> relative path - this was then made absolute using the search paths.
> 1.4.0 always returns null in this case.
> We should restore the old behaviour



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

[jira] [Closed] (SLING-5492) ResourceResolver#getParent might ask wrong resource provider

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5492.
---

> ResourceResolver#getParent might ask wrong resource provider
> 
>
> Key: SLING-5492
> URL: https://issues.apache.org/jira/browse/SLING-5492
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> ResourceResolver#getParent always uses the resource provider of the current 
> resource to get the parent resource. However, the parent resource might be 
> delivered by a different provider



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

[jira] [Closed] (SLING-5521) Support Closeable for provider state

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5521.
---

> Support Closeable for provider state
> 
>
> Key: SLING-5521
> URL: https://issues.apache.org/jira/browse/SLING-5521
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Resource 2.7.2, Resource Resolver 1.4.2
>
>
> To prevent from potential memory leaks we should support Closeable for the 
> provider state: if a resource resolver is still open while a resource 
> provider is unregistered, the provider becomes unavailable and can't be 
> called for logout anymore.
> However, the resource resolver still holds the provider state and can call 
> methods on it. Therefore we could support ading close() if the state object 
> implements Closeable and proberly cleanup (given that the state object itself 
> can clean up)



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

[jira] [Closed] (SLING-5495) Resolution path is not always set

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5495.
---

> Resolution path is not always set
> -
>
> Key: SLING-5495
> URL: https://issues.apache.org/jira/browse/SLING-5495
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> Due to the refactoring, we missed some places where the resource metadata 
> needs to be set, especially the resolution path



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

[jira] [Closed] (SLING-5497) ResourceResolver#getResource(Resource, String) should handle a null path returned by the base resource

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5497.
---

> ResourceResolver#getResource(Resource, String) should handle a null path 
> returned by the base resource
> --
>
> Key: SLING-5497
> URL: https://issues.apache.org/jira/browse/SLING-5497
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> The implementation before 1.4.0 handled 
> ResourceResolver#getResource(Resource, String) called with a resource 
> returning null for getPath
> The new implementation is throwing an NPE
> We should handle the case and treat it like a null rsource



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

[jira] [Closed] (SLING-5493) Stateful resource resolver should not hold (stateless) resource provider

2016-02-19 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler closed SLING-5493.
---

> Stateful resource resolver should not hold (stateless) resource provider
> 
>
> Key: SLING-5493
> URL: https://issues.apache.org/jira/browse/SLING-5493
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.4.2
>
>
> The stateful resource resolver (AuthenticatedResourceProvider) should not 
> hold the stateless ResourceProvider instance as this might get unregistered 
> while the resource resolver is still in use



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

40 matches

Mail list logo