Hi,
On Tue, Jan 5, 2016 at 4:48 PM, Bertrand Delacretaz
wrote:
> ...This is about creating service users and setting ACLs for SLING-5355...
FYI I have thought a bit more about this and broadened the scope a bit
to include other things that need to be initialized in the content
repository, and ma
On Wednesday 06 January 2016 14:34:04 Bertrand Delacretaz wrote:
> Hi,
>
> On Wed, Jan 6, 2016 at 11:54 AM, Oliver Lietz wrote:
> > On Wednesday 06 January 2016 11:33:03 Bertrand Delacretaz wrote:
> >>... a) tweak the provisioning model tools so that a new ProvisioningModel
> >>
> >> service make
Hi,
On Wed, Jan 6, 2016 at 11:41 AM, Carsten Ziegeler wrote:
> Bertrand Delacretaz wrote
>> b) implement a component to process :basetree additional sections...
>> c) implement a component to process :accesscontrol sections...
> ...the only comment I have is whether we really need
> to separate
Hi,
On Wed, Jan 6, 2016 at 11:54 AM, Oliver Lietz wrote:
> On Wednesday 06 January 2016 11:33:03 Bertrand Delacretaz wrote:
>>... a) tweak the provisioning model tools so that a new ProvisioningModel
>> service makes the content of :additional model sections available as
>> unprocessed full text
On Wednesday 06 January 2016 11:33:03 Bertrand Delacretaz wrote:
> Hi,
Hi,
> On Wed, Jan 6, 2016 at 10:59 AM, Carsten Ziegeler
wrote:
> > ...Perfect :) ..
>
> Ok, glad that we agree!
>
> So how about the following implementation based on the above 3 requirements:
>
> a) tweak the provisionin
Bertrand Delacretaz wrote
> Hi,
>
> On Wed, Jan 6, 2016 at 10:59 AM, Carsten Ziegeler
> wrote:
>> ...Perfect :) ..
>
> Ok, glad that we agree!
>
> So how about the following implementation based on the above 3 requirements:
>
> a) tweak the provisioning model tools so that a new ProvisioningM
Hi,
On Wed, Jan 6, 2016 at 10:59 AM, Carsten Ziegeler wrote:
> ...Perfect :) ..
Ok, glad that we agree!
So how about the following implementation based on the above 3 requirements:
a) tweak the provisioning model tools so that a new ProvisioningModel
service makes the content of :additional mo
Bertrand Delacretaz wrote
> Hi Carsten,
>
> On Wed, Jan 6, 2016 at 9:56 AM, Carsten Ziegeler wrote:
>> we should keep constraints and conclusions separate!...
>
> So let's try to focus on the high-level requirements, I see this:
>
> 1) Create service users and set their ACLs as defined in t
Hi Carsten,
On Wed, Jan 6, 2016 at 9:56 AM, Carsten Ziegeler wrote:
> we should keep constraints and conclusions separate!...
So let's try to focus on the high-level requirements, I see this:
1) Create service users and set their ACLs as defined in the Sling
instance's provisioning model.
Sorry, but I don't agree on the new added constraints and their
conclusion - we should keep constraints and conclusions separate!
- AC1: Waiting for content paths: not all ACLs can be applied
immediately when the SlingRepository service starts: for this we'd need
to create paths that don't exist
Bertrand Delacretaz wrote
> Hi,
>
> This is about creating service users and setting ACLs for SLING-5355.
> I think it's easier to discuss these general principles here.
>
> Carsten wrote there:
>
>> I would prefer a solution which is processed by the tool processing the
>> provisioning model
>
Hi,
This is about creating service users and setting ACLs for SLING-5355.
I think it's easier to discuss these general principles here.
Carsten wrote there:
> I would prefer a solution which is processed by the tool processing the
> provisioning model
> and then creating "content" which is inst
12 matches
Mail list logo
