Return-Path: Delivered-To: apmail-portals-jetspeed-dev-archive@www.apache.org Received: (qmail 52860 invoked from network); 16 Jan 2010 12:01:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Jan 2010 12:01:49 -0000 Received: (qmail 27154 invoked by uid 500); 16 Jan 2010 12:01:48 -0000 Delivered-To: apmail-portals-jetspeed-dev-archive@portals.apache.org Received: (qmail 27085 invoked by uid 500); 16 Jan 2010 12:01:48 -0000 Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@portals.apache.org Received: (qmail 27075 invoked by uid 99); 16 Jan 2010 12:01:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jan 2010 12:01:48 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [212.227.17.9] (HELO moutng.kundenserver.de) (212.227.17.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jan 2010 12:01:40 +0000 Received: from [192.168.1.3] (c-24-7-68-235.hsd1.ca.comcast.net [24.7.68.235]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0Lp8j6-1O1tn60lzI-00fSdl; Sat, 16 Jan 2010 13:01:17 +0100 Message-ID: <4B51AB3D.9040306@wemove.com> Date: Sat, 16 Jan 2010 04:04:13 -0800 From: =?ISO-8859-1?Q?Joachim_M=FCller?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0 MIME-Version: 1.0 To: jetspeed-dev@portals.apache.org Subject: Re: New User/Group/Role Management Portlet References: <4B4D0848.5090801@wemove.com> <252069.92269.qm@web51106.mail.re2.yahoo.com> In-Reply-To: <252069.92269.qm@web51106.mail.re2.yahoo.com> X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Provags-ID: V01U2FsdGVkX1+UxWfJ5LScPDIOF9qCVHB4MgWxdq5x1HUUso6 r/dEKwu8bUwrRXXNlROKhGAbFyFpawS6+RiO4fwEM8E+vc/FEX TZTDn4v8IPuODQm6UNIv54AZO56YRiE Hi Woonsan, thanks for the comments. I did check out the "upcoming" OJB 1.0.5 as well but the "upcoming" takes time since the 1.0.5-rc1 version was released at 29-Jan-2008 and the last commit on the project was on 31-Jan-2008. It seems OJB is a dead project. The other option would be to wait until the JPA integration is there. But I think this is a major change and therefore not to be expected in the very near future. (I think Randy was already working on this already...) And last but not least I wanted to create a 2.1.4 compatible solution to be backported. I am perfectly sure that this will be an intermediate solution for the trunk until the JPA implementation is there, but I think the current solution needs to be upgraded ASAP, because it is not suitable for installations with big numbers of users (no database level paging support). Regards, Joachim Am 15.01.2010 07:01, schrieb Woonsan Ko: > Hi Joachim, > > Please see my comments below. > > > > ----- Original Message ---- >> From: Joachim M�ller >> To: Jetspeed Developers List >> Sent: Wed, January 13, 2010 12:39:52 AM >> Subject: New User/Group/Role Management Portlet >> >> 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 tried to search any framework level support for the DBMS-side pagination queries. > OJB seems now ready to support that feature since 1.0.5. It has been added with this issue: http://issues.apache.org/jira/browse/OJB-131 > Also, I had a look at some source codes such as PlatformOracleImpl [1], PlatformMySQLImpl and PlatformPostgreSQLImpl (in the package, org.apache.ojb.broker.platforms). Each one seems to use its own platform specific ones: rownum/rnum for oracle, LIMIT for MySQL, etc. > You could have a look at those in addLimitSql() method and addPagingSql() method in each class. > I think we can ask OJB team to make a release of 1.0.5 and we'd better use new OJB or any other framework having same features. > > [1] https://svn.eu.apache.org/repos/asf/db/ojb/branches/OJB_1_0_RELEASE/src/java/org/apache/ojb/broker/platforms/PlatformOracleImpl.java > > Kind regards, > > Woonsan > >> >> I am planing to plug the JetspeedPrincipalLookupManager into the >> JetspeedSecurityPersistenceManager via Spring. >> >> Any comments on that plan? Anything I have to be aware of? >> >> Thanks for any comment, >> Joachim >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org >> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org > For additional commands, e-mail: jetspeed-dev-help@portals.apache.org > > -- < joachim m�ller joachim@wemove.com wemove digital solutions gmbh eschersheimer landstr. 5-7 60322 frankfurt am main amtsgericht frankfurt am main, hrb 53992 gesch�ftsf�hrer joachim m�ller, stefan hartmann --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org For additional commands, e-mail: jetspeed-dev-help@portals.apache.org