[Cosmo-dev] acegi ACL implementation - more thoughts

[Brian Moseley]

On 11/21/06, Vinubalaji Gopal <vinu at osafoundation.org> wrote:

> 1. For providing the hibernate based acl implementation we could provide
> an external mapping. We could even use Hibernate annotations to provide
> the mapping but that will involve changing the base classes and I want
> to avoid that. As Cosmo has the hibernate annotation based mapping now,
> do you feel that having a combination of xml mappings and annotations
> mapping is acceptable?

i'd rather use one mapping mechanism, and the annotations are REALLY
nice. what base classes are you referring to - the acegi ones?

> 2. There has been some interests on the acegi forum about the hibernate
> based acl implementation (old implementation)
> http://forum.springframework.org/showthread.php?t=13956
> http://forum.springframework.org/showthread.php?t=13956

hm. after reading over that, i'm almost tempted to just stick with
acegi's jdbc stuff and not worry about hibernate for acls. here's a
thought:

   - define o.o.c.dao.AclDao interface
   - add a AclDao dependency to UserService and ContentService
   - provide a o.o.c.dao.acegi.AcegiJdbcAclDao adapter to acegi's
dbcExtendedDaoImpl

this seems like the least amount of work that isolates our acl
persistence implementation from our service implementations.

> 3. Acegi 1.0.3 is out :). It includes the new acls from acegi's sandbox.
> It did not work out of the box and I would like to know the changes to
> make it work with Cosmo. I am aware there is a bug to upgrade to the
> latest acegi, but if its documented/trivial to do, I could do that.

i haven't looked into the upgrade yet. upgrading spring and acegi are
a lower priority than our newer feature work, so it's possible they'll
slip to the next release. if you want to give the acegi upgrade a try
and provide a patch, that would certainlly be helpful :)