Hello Serge,

thanks for the suggestion.

The next problem is on the definition side. We would like to let the template designer define, which groups should be assigned to the new page, conainer lists, containers and fields and which permissions they should have. Do we have to develop our own tags or APIs for the definition and then store this metadata in our own tables and caches or is there something in Jahia we can use or reuse?

Regards,
Benjamin

Serge Huber <[EMAIL PROTECTED]> wrote on 15.07.2004 14:15:18:

>
> Hi Benjamin,
>
> My suggestion would be to use Jahia event listeners to set the ACLs
> when the new content is created. The listeners are configured
> through the WEB-INF/etc/config/listeners.registry file, and you can
> find there examples of listeners.
>
> As far as the API is concerned you should find a lot of what you
> need on org.jahia.services.acl.JahiaACL and JahiaBaseACL.
>
> Regards,
>   Serge Huber.
>
> At 13:01 15.07.2004, you wrote:

> We got the info that it is possible to assign the ACL dynamically
> from within the templates or portlets directly through the Jahia
> API. We would like to make that, but still use the container-engine
> to add/update/delete the container. We want to remove the Rights tab
> from the view and automatically assign groups (which have been
> defined manually) and permisstions to the containers, pages and
> fields. In the template we are for now declaring the container
> lists, containers and fields and we are trying to use as many Jahia
> tags and JSTL instead of the scriplets. What is the best and most
> elegant way to add programmatic ACL assignment?
>
> Benjamin Papez

> - -- --- -----=[ serge.huber at jahia dot com ]=---- --- -- -
> Jahia : A collaborative source CMS and Portal Server
> www.jahia.org Community and product web site
> www.jahia.com Commercial services company

Reply via email to