On 17 Dec 2008, at 03:59, Rory Douglas wrote:
As for the AccessManager, I think there are plans to upgrade Sling
to Jackrabbit 1.5, so it may be more worthwhile to wait for that &
use the repository-ACL-based AccessManager that comes with 1.5
rather than implementing your own. Or ping me
Hi Sebastian
I went this route back in August, and came up against the same problems
(see [1]). I had the AccessManager working by exporting the .spi
classes from Sling's Jackrabbit bundle, but would intermittently run
into issues with the JAAS LoginModule after restarts. I think there may
Hi everyone.
I'm trying to secure the JCR repository creating a custom LoginModule and
AccessManager. The first one has gone OK, as it implements the JAAS standard
interface. On the other hand, the second one must implement Jackrabbit's
AccessManager interface, but as Sling's Jackrabbit Embedded Re
[
https://issues.apache.org/jira/browse/SLING-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656985#action_12656985
]
Carsten Ziegeler commented on SLING-766:
Changed this in revision 727047:
Don't uni
[
https://issues.apache.org/jira/browse/SLING-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-781.
---
Resolution: Fixed
Committed initial version in Rev. 727044.
> Add Web Console Plugin for the
Add Web Console Plugin for the new ResourceResolver
---
Key: SLING-781
URL: https://issues.apache.org/jira/browse/SLING-781
Project: Sling
Issue Type: Bug
Components: JCR Resource
Felix Meschberger wrote:
> Hi,
>
> Bertrand Delacretaz schrieb:
>> On Tue, Dec 16, 2008 at 8:21 AM, Felix Meschberger
>> wrote:
>>> ...The JSTL is not included in the scripting/jsp project and must be
>>> deployed separately.
>>>
>>> But it would probably make sense to include it with out
>>> sc
Hi,
Bertrand Delacretaz schrieb:
> On Tue, Dec 16, 2008 at 8:21 AM, Felix Meschberger wrote:
>> ...The JSTL is not included in the scripting/jsp project and must be
>> deployed separately.
>>
>> But it would probably make sense to include it with out
>> scripting/jsp-taglib bundle
>
> Or as
On Tue, Dec 16, 2008 at 8:21 AM, Felix Meschberger wrote:
> ...The JSTL is not included in the scripting/jsp project and must be
> deployed separately.
>
> But it would probably make sense to include it with out
> scripting/jsp-taglib bundle
Or as a specific script/jsp-jstl bundle? That would