This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
My question is, for above 2 user tasks what is the standard best approach being used these days? Should I create tables in database and write code to maintain above information or is there a better approach available?
You have to maintain information (what exactly you call information is application specific, I feel). So you will have to use some kind of persistence mechanism (database is a good choice considering the advantages it provides). You mentioned you are using hibernate (hibernate is an ORM, Object to Relational mapping tool). So its obvious you ought to have a database, right? Is there anything specific you have in mind?
Joined: Jul 10, 2008
So its obvious you ought to have a database, right? Is there anything specific you have in mind?
Thanks for reply Raj. Actually I am thinking "Managing User Profiles, login and password" is a pretty standard problem, so there could be a standard solution available out of the box. Is everybody writing new code in every project to handle this problem?