On Tue, Jan 12, 2010 at 3:39 PM, Joachim Müller <[email protected]> wrote:
> Hi, > > I want to create new User/Group/Role Management portlets that are easier > to use/understand. The main requirements are: > > - easy to understand UI > - simple but powerful query interface > - paging for the principal results list > - be able to work with 10.000+ users in terms of memory/performance > > To accomplish the requirements I would like to introduce a > JetspeedPrincipalLookupManager with the method: > > JetspeedPrincipalResultList getPrincipals(JetspeedPrincipalQueryContext > queryContext); > > The JetspeedPrincipalQueryContext holds all possible query parameters > (principal name, attributes, asscoiatedRoles, asscoiatedGroups, > asscoiatedUsers, sort order, paging parameters, etc.). > > The JetspeedPrincipalResultList encapsulates the actual list of detached > JetspeedPrincipals and the total number of results. > > The JetspeedPrincipalLookupManager will be implemented using plain JDBC > because paging the result set is not/poorly supported by OJB. Database > specific LookupManager implementations can be plugged in via Spring and > can handle database supported paging (like MySqls LIMIT) but there is a > default implementation that uses plain JDBC for paging the result set. > The DB platform is derived from OJB, there is no extra config parameter > to take care of. > > I am planing to plug the JetspeedPrincipalLookupManager into the > JetspeedSecurityPersistenceManager via Spring. > > Any comments on that plan? Anything I have to be aware of? > > +1
