You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by "Reinhard Poetz (JIRA)" <ji...@apache.org> on 2006/04/10 12:10:58 UTC

[jira] Closed: (COCOON-1769) Role Handling

     [ http://issues.apache.org/jira/browse/COCOON-1769?page=all ]
     
Reinhard Poetz closed COCOON-1769:
----------------------------------

    Resolution: Won't Fix

solved by using Spring

> Role Handling
> -------------
>
>          Key: COCOON-1769
>          URL: http://issues.apache.org/jira/browse/COCOON-1769
>      Project: Cocoon
>         Type: Sub-task

>   Components: - Blocks Framework
>     Reporter: Daniel Fagerstrom

>
> The concept of role handling is Avalon specific, so it doesn't work that well if we want to register e.g. our sitemap components as OSGi services or Spring components. Maybe we could just put the role info in the container as well so that we don't need to maintain a parallel  set of rolemanagers for the blocks. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira