Message-ID: <772420894.90835.1397828357171.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_90834_1153837672.1397828357170" ------=_Part_90834_1153837672.1397828357170 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A simple user management library. Contains a simple user model and a cou= ple of DAOs, profile and password management components. Current dao implem= entations are hibernate-based. Should happily replace OSUser.=20
Berkano-user was started long ago, then re-used once I got disapointed w= ith osuser. Still has a couple of old classes or ideas here and there, need= s clean up and polishing.=20
Berkano-user defines a couple of interface for users, groups, permission=
s, membership management. Much like os-user does, but maybe with a more &qu=
All these are based on the principles o= f IoC, using CDI (constructor dependency injection). I'm personally using P= icoContainer, but I believe Spring or any other ioc container should be usa= ble as well.
You will need to declare the implementations you want to= use to your container.
There is currently a single implementation, w= hich is based on Hibernate.
Foreseen implementations could be JDO(is = this still alive?), EJB3 (maybe the Hibernate implementation could fulfill = both needs?), plain SQL(do we really want to maintain this?), LDAP, and del= egators to application servers' authentication APIs.
Berkano User UI for WebWork provides= an UI for this.
Berkano-user defines simple interfaces to define the preferences that an=
application wants to expose to the end-user, ie what properties s/he can f=
reely modify to suit his needs.
Berkano User UI for WebWork provides an UI for this purpose= .
Berkano-user also defines interfaces and a couple of implementations for==20