I don't understand why you want so hard to mutualize a set of POJOs + an hibernate configuration. It's trivial software to write. In portal world, a lot of things are done rather around LDAP and database is a good default option (for out of the box). "tom.baeyens(a)jboss.com" wrote : "sohil.shah(a)jboss.com" wrote : tom- | | | | what you are talking about at this point is the Identity Management Framework. As far as the ACL component is concerned (topic of discussion in this thread), it should be Identity Management Framework agnostic with ability to plugin different Identity Management implementations. | | | | Thanks | | if i understand you correctly, that is exactly the opposite of what I'm trying to promote. | | i think we can build 1 implementation so that all the projects can leverage it as an implementation for project specific identity interfaces. | | that way, in the platforms, it would be possible to configure all the components to use 1 and the same component implementation. | | at a minimum, a database schema has to be defined so that we all can work with a single DB repository. And IMO, a set of POJO's+hibernate mappings should accompany the common identity database schema. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098350#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...