My suggestion : Wicket / Spring / Cayenne ORM
________________________________
From: Josh Kamau <joshnet2...@gmail.com>
To: users@wicket.apache.org
Sent: Mon, October 4, 2010 1:37:45 PM
Subject: Re: New App - Best Practices
I use Wicket/Guice/JPA-Hibernate.
I think you will have to do alot of evaluation of the technologies yourself.
You have wicket for the presentation, now find a DI container and an ORM
solution and you are sorted. Normally the Presentation layer is the hard
part to decide when you are a java developer but you seem to have that taken
care off.
regards.
On Mon, Oct 4, 2010 at 1:15 PM, Sam Stainsby <s...@sustainablesoftware.com.au
> wrote:
> On Mon, 04 Oct 2010 17:49:07 +1000, Chris Colman wrote:
>
> >>You are also missing out on advantages like automatic schema updates,
> >>DB4O's own unique ID system, and other very useful parts of the DB4O
> > API.
> >
> > The way I use JDO I get all of those features but in a datastore
> > agnostic way.
>
> This is really interesting, albeit your solution uses non-open source
> tools that I could not specify as a dependency in our open source
> framework. We also didn't discuss DB4O's native queries, which are
> optimised on the fly, but we are wandering further off-topic, so I will
> send an email.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
