Hi,
our main web site is now powered by the Apache CMS (thanks to everyone
involved, especially to Felix), however we still have the old web site
available and it seems that in some cases the content in the Apache
CMS does not reflect the latest result from the old site.
This means we have to
[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13599807#comment-13599807
]
Carsten Ziegeler commented on SLING-2782:
-
Right now e.g. creating a folder
[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13599811#comment-13599811
]
Bertrand Delacretaz commented on SLING-2782:
Agreed, this does make sense for
[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13599812#comment-13599812
]
Felix Meschberger commented on SLING-2782:
--
I think the killer case is that the
From: Felix Meschberger [mailto:fmesc...@adobe.com]
Okay, as far as I understand we've got the consensus of separating my
access gate
proposal from the Sling API. We should have something like a
ResourceAccessSecurity
service in a extension bundle,
I think we can keep the basic
Hi
To be sure (and save some time coding ;-) ), I sum up our discussion:
We can keep the basic singleton service (ResourceAccessSecurity) in the API
and document it like this:
* Expected to only be implemented once in the framework/application
(much like the OSGi LogService or
Bertrand Delacretaz created SLING-2785:
--
Summary: ResourceMetadata.entrySet() and related methods cause
stack overflow when locked
Key: SLING-2785
URL: https://issues.apache.org/jira/browse/SLING-2785
Lukas Eder created SLING-2786:
-
Summary: ResourceMetadata contains stale unmodifiableMap cache
after clone()
Key: SLING-2786
URL: https://issues.apache.org/jira/browse/SLING-2786
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13599952#comment-13599952
]
Carsten Ziegeler commented on SLING-2786:
-
We'll never add an unlock operation
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1592/
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1592/
See https://builds.apache.org/job/sling-trunk-1.6/changes
See https://builds.apache.org/job/sling-trunk-1.6/changes
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.base/1593/
[
https://issues.apache.org/jira/browse/SLING-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600048#comment-13600048
]
Carsten Ziegeler commented on SLING-2779:
-
I think we shouldn't define the
[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1364#comment-1364
]
Bertrand Delacretaz commented on SLING-2782:
I have added rendering tests in
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1593/
[
https://issues.apache.org/jira/browse/SLING-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600028#comment-13600028
]
Bertrand Delacretaz commented on SLING-2786:
I agree about clone(), feel free
hi carsten
just to clarify, the ResourceProviderDecorator is not a proposal for
security - it's a proposal for extensibility.
i tend to disagree. as lars already explained in this thread before
you can't have extensibility when it comes to access control and
permissions without messing with
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/1593/
Lukas Eder created SLING-2787:
-
Summary: Inefficient array conversion in
ValueMapDecorator.convertToArray()
Key: SLING-2787
URL: https://issues.apache.org/jira/browse/SLING-2787
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13600069#comment-13600069
]
Carsten Ziegeler commented on SLING-2782:
-
Do we need a whitelist or a blacklist?
[
https://issues.apache.org/jira/browse/SLING-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Eder updated SLING-2787:
--
Attachment: ValueMapTest.java
ValueMapDecorator.java.patch
Inefficient array
Antonio Sanso created SLING-2788:
Summary: Sling running using Apache OAK
Key: SLING-2788
URL: https://issues.apache.org/jira/browse/SLING-2788
Project: Sling
Issue Type: Wish
[
https://issues.apache.org/jira/browse/SLING-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-2785.
Resolution: Fixed
Fixed in revision 1455511.
P.S. I like Wittekop, and generally
Oliver Lietz created SLING-2789:
---
Summary: deploying Sling 7-SNAPSHOT on Karaf fails
Key: SLING-2789
URL: https://issues.apache.org/jira/browse/SLING-2789
Project: Sling
Issue Type: Bug
26 matches
Mail list logo
