Erik, I'd certainly be happy for you to do that :) On Wed, Jul 29, 2009 at 3:38 PM, Erik Post <eriksen...@gmail.com> wrote:
> Hi Jeremy, > > Just to weigh in on this, I personally think that working with JPA > entity managers/Hibernate sessions could do with some clarification > beyond "just use Spring". There are a number of quickstart type > projects out there, but they all seem to revolve around using Spring, > whereas I would have liked to see some of the more low level concepts > cast light on, as they apply to Wicket: > > - Why might one want to use OSIV or other patterns? > - EntityManagers/Sessions: how to obtain/close > - Where in the app/request lifecycle do you do stuff? > - Potential lazy loading issues > - Using thread-local storage > - How/where does this tie into servlets? > - Why you might not want to bother with all of this too much and just > use Spring/EJB instead. > - etc. > > Most of this is not specific to Wicket per se, and I've seen a couple > of posts on this in the mailing list/various blogs floating around, > but it's quite a lot of stuff to piece together. I think a > comprehensive treatment of these issues would be useful. > > Having typed all of that, maybe I should just write a tutorial > myself... Oh well, my 2c. > > Cheers, > Erik > > > On Wed, Jul 29, 2009 at 11:55 PM, Jeremy > Thomerson<jer...@wickettraining.com> wrote: > > I'd be interested in knowing from your viewpoint what parts had a high > > learning curve? And what background are you coming from (that may > > effect your individual curve)? In my experience, Wicket has a MUCH > > lower learning curve than Spring Web Flow and Tapestry (any > > incarnation). So, as someone who teaches Wicket, I'd be interested in > > seeing what parts stumped you. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
