Skip to end of metadata
Go to start of metadata

A simple user management library. Contains a simple user model and a couple of DAOs, profile and password management components. Current dao implementations are hibernate-based. Should happily replace OSUser.

Berkano-user was started long ago, then re-used once I got disapointed with osuser. Still has a couple of old classes or ideas here and there, needs clean up and polishing.

User management

Berkano-user defines a couple of interface for users, groups, permissions, membership management. Much like os-user does, but maybe with a more "modern" architecture.
All these are based on the principles of IoC, using CDI (constructor dependency injection). I'm personally using PicoContainer, but I believe Spring or any other ioc container should be usable as well.
You will need to declare the implementations you want to use to your container.
There is currently a single implementation, which 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 delegators to application servers' authentication APIs.
User Datamodel
Berkano User UI for WebWork provides an UI for this.

User Preferences

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 freely modify to suit his needs.
Read more.
Berkano User UI for WebWork provides an UI for this purpose.

Passwords

Berkano-user also defines interfaces and a couple of implementations for

  • No labels

2 Comments

  1. Looks really interesting i've been trying to gather information concerning OSUser but have been unable to find enough to start integrating it with my Tomcat deployed web application.

    Do you have documentation regarding how to setup Berkano with Spring and which configuration would be required?

  2. Javed,
    Unfortunately, no doc for Spring integration right now, for the simple reason that I never used Berkano w/ Spring. Feel free to try out. If you know how Pico works, I'd try it out with Pico first (at least the few docs here and I will be able to help out), then try to migrate towards Spring. One of the things that will probably require some fiddling around is that the Hibernate DAOs rely on an Hibernate Session being injected into the constructor, which is a feature provided by Nanocontainer-Persistence. Not sure Spring provides something similar. Some coding will probably be needed. (Either on Spring side or on Berkano's side, like wrapper/adapters which would feed the DAOs through whatever Spring provides)