On Thu, 31 Jul 2003, Peter Paulus wrote:
You should know that the Slide block within Cocoon isn't finished, and
need help from third persons.
> This Vector is passed as an Enumeration to getPrincipals(). getPrincipals()
> then processes that as follows:
>
> ...
> // FIXME the CVS code from slide does only implement getRoles
> Enumeration roles = this.security.getRoles(userobject);
> String role = null;
> if (roles.hasMoreElements())
> {
> role = (String) roles.nextElement();
> }
> ...
>
> the postcondition of this code is that role is either the null-object or a
> String with contents 'nobody'.
>
> I think there are a number of improvements to make:
>
> 1. I suppose the role 'nobody' is assigned to everybody. Why would you want
> to make this role explicit? Having no configured roles, means having role
> 'nobody'.
>
> 2. There is a decrepancy in the modelling for principals between Slide and
> Cocoon. In Slide a user can have 1 or more roles (?, see remarks further
> on). In Cocoon a user has zero or 1 role.
This comes from the fact that I wanted to use the authentification
framework from Carsten, which currently only one role supports.
> 5. I not sure whether order of the vector is important. But if it is, and it
> seems so for Cocoon, could then the order of the Class.getInterfaces() be
> different on different Virtual Machines?
>
> And suppose that every Virtual Machine maintains the order as specified in
> the source file. How can one guarantee that future developers specify the
> intended order?
At the moment the future of the Slide block is unclear. I have implemented
a first bridge between Slide and Cocoon, but this seems more to be a
one-man show. To keep this block alive I need support from others.
So, if you want to enhance the code base, when are patches welcome.
Stephan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
