> Feel free to login using jetspeed defaults (admin/jetspeed) edit a user > > groups/roles and add/edit groups and roles. > > > > I had little time to look at it, but what strikes me is that I expected > a user would have 0 or more roles in each group, and the user interface > seems to assume 0-1 role per user in each group.
Yes, it's obvious after logging in to the site (http://epyna.syros.aegean.gr:8080/jetspeed). I think that this is just user interface issue though. The code probably supports 0-n roles per group? > > It would be great to discuss cleanly the semantics and use cases before > committing code (unless it is in an alternate and optional security > service). > I agree. One scenario that I would like to implement would be a portal for multi-department entity. Each department would publish their home page via /group/${department_name}/page/default.psml. This page would be: 1. view only for the anonymous user 2. view+info+print for any user with role 'user' in ${department_name} group 3. all access for any user with role 'admin' in ${department_name} group But that is just one usecase. > > > By the way, I would like to ask you a question. We have put that to a > > slackware Linux and that's why you are going to see some problems on > > jetspeed. Can anyone give an explanation pls? > > > > The problem I see is related with xalan, which should be put in the > endorsed dir, either in tomcat or in the jdk dir (1.4 related) This should finally make it into the FAQ. Best regards, Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
