Hi Roland and Erik Thanks for your replies, notably the "best practices" provided.
Regarding the way to design, I would sum your answers as following : - one can follow a "Domain Driven Design", with a manager per kind of object. - In the Spring ApplicationContext file, I should only define implementations and in my Java code I should only use interfaces. Is that correct ? I will have a look at Wicket Pastebin source code to see how they did, but I don't know what design they followed and if it's well implemented. Can you give me an idea about it ? For the time, I guess I'll avoid spring javaconfig, I tend to progress quite slowly so... lol BTW, could you advice me some goods books on the topic ? I'm reading a french book on it, but it doesn't detail the design aspects of it... Thanks in advance ZedroS ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
