I've used it also, but it changed source availability, licensing and code
repositories too many times to my taste, and I'm trying to remove it from
all my code. I would consider a solution like that if it was a little more
mainstream, widely used and with a supporting community. To date, I haven't
found a better alternative, but would be very glad to find it.Cheers, Daniel T Ames wrote: > > I use a product called JPersist - no XML, just POJOs. Has built in > pooling. > I instantiate the DatabaseManager in the web application and use a getter. > > http://www.jpersist.org > > It has a list of tested databases, but I use Microsoft SQL. Haven't had > too > many issues with it. > > On Tue, Oct 6, 2009 at 5:34 AM, Peter Arnulf Lustig > <uuuuu...@yahoo.de>wrote: > >> What's the fast and easy way? >> >> I am asking because of a lot of trouble with hibernate. >> >> > -- View this message in context: http://www.nabble.com/How-do-you-achieve-persistency-tp25765566p25776501.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
