I did something like that a while ago to add new user profile categories and properties. It is actually quite involved for a seemingly minor change. Not sure if it is the proper way. I asked around at the time but not much input about how to do this efficiently. So I end up doing something similar to the
as far as I know, all the way that you have done are ok.
the question is : how far do I need to modify the way the user are managed in the GateIn portal as it is delivered, to get what I need for my UseCase.
you can find some more about this question is this post (and in my messages for that topic) :
in particular in point : "5 ) Business Process application of the companies"
The point is : GateIn is provided with some pages and user interface to manage the users.
but with a simple and general user management.
some portal project may need to extend, adapt, reshape the User entity and the user interface for the management of user/role/group/permission.
for some projects, the requierments about users are so large that it is better to recode a whole user interface to manage the users.
then it can be done starting from the GateIn elements, or from stratch.
as far as the Identity Service contract is compliant, GateIn will find the user information it needs, and work with that.
even if the User is extended, modified in some part, etc...
that the interesting thing with the Identity Management project, and the service to provide the users information, independant from the way to manage them.
one thing to note : what about your modifications, form the GateIn elements, when a new version of GateIn comes ?
re-adapt the GateIn element for each upgrade is a burden : this must be taken into account in the decision to use a whole custom user management in your portal...
hope it helps,
JBoss Portal and GateIn (JSR-286), JSF, Richfaces, J2EE, Drools, BRMS.
I think the user profile management in Jboss Portal was superior to that in GateIn now. In the old Portal you could specify the user properties via xml. Now it seems you really have to dig deep and modify some underlying classes - which of course brings the question what will happen when a new version is released.
I would really appreciate if there would be a strategy to go back to the xml configuration. I bet that this will bite the developers in most enterprise projects as the customers will of course have detailed requirements on which profile data should be used. So user profile modifications is a natural part in all portal projects.
in your post http://community.jboss.org/thread/152294 you referred to you still had questions. Could you update a bit how you finally ended up with your customizations?