The pojos are great, it's the save and load methods that I was referring to.
-Igor > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Timo Stamm > Sent: Friday, October 07, 2005 4:43 PM > To: [email protected] > Subject: Re: [Wicket-user] Standard for database integration? > (Please!) > > Igor Vaynberg wrote: > > Having code like this > > > > Class Person { > > private long id; > > private String username; > > private String firstname; > > private String lastname; > > > > ...getters/setters... > > > > public void save() {...} > > public void loadById(long id) {...} > > } > > > > Can be done with anything from hibernate to db40 to jdbc - > its still a > > poor way to write an application. > > > I don't like having to create a class for each data entity. > On the other hand, those bean-style POJOs are very common and > supported by various frameworks. > > Can you give reasons for your opinion? > > > Timo > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, > discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
