Jon Stevens wrote:

> > ouch. this was discussed before. what about "UserGroup", I'd like to keep
> > class
> > name though (we have 'User' class and 'Visitor' table...)
> 
> I still don't like it. What is your dislike of "Team"...group and team are
> the same thing.

Oh maybe it's just me not being native speaker. For me 'a team of people entitled
to press a button' souds silly. 
On the other hand, it seems the cleanest soulution because of 'group' being reserved
word in SQL. I take back 'UserGroup' proposal. It would be very misleading. 
If none better alternatives show up, I'll rename it to Team in a few days.

I think that we could also rearange the DB schemas.
Visitor -> User
UserRole -> Role
VisitorRole -> UserTeamRole

We should also decide what to do with the columns of Visitor (User) table.
It's not practical to try including there all fields that applications would
need. Such special attributes should be kept in Perm (objectData). On the
other hand we need to have the attributes that are likely to be used for
looking up an user as column (LDAP attributes), because otherwise they
couldn't be used in queries.

I think that {loginId, firstName, lastName, email} is the minimal set of
attributes that is useful for queries. Any other sugestions?

When we have this set of fields, we can define constants with names in
SecurityService interface, and add getUser( Criteria ) method.

Then, SecurityService implementations must map those names to actual
column/attribute names and perform the query. It's perfectly possible
to write a method for creting LDAP queries from Criteria objects.
for example.

Criteria criteria = new Criteria();
criteria.add( SecurityService.FIRST_NAME, "Jon");
criteria.add( SecurityService.LAST_NAME, "S%", Criteria.LIKE);

would yield the following LDAP query
&(givenName=Jon)(sn=S*)

...

It's a beautiful morning, and I have lot of cool stuff to hack on.
Feels good :)

Rafal


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to