Martijn, It is so nice of you to reply to my questions. One question I have about your book:
The bottom of Page xxi says: .. from Terracotta for giving Wicket a vaiable scaling strategy. What do you exactly mean by that? Do you mean Terracotta makes the stateful programming model less of a concern in terms of memory consumption? Regards, David --- On Fri, 2/5/10, Martijn Dashorst <[email protected]> wrote: > From: Martijn Dashorst <[email protected]> > Subject: Re: Fix super(new CompoundPropertyModel(this)) error in the WIA book > To: [email protected] > Date: Friday, February 5, 2010, 7:09 AM > On Fri, Feb 5, 2010 at 10:16 AM, > Wilhelmsen Tor Iver <[email protected]> > wrote: > >> super(new CompoundPropertyModel(this)); > > > > This seems wrong: A call to super() cannot reference > "this" directly or indirectly: > > > > JLS §8.8.7 says: > > "It is a compile-time error for a constructor to > directly or indirectly invoke itself through a series of one > or more explicit constructor invocations involving this." > > Yup, this is a bug in the book's example code. Has nothing > to do with > 1.3 or 1.4. > > And yes, the book is still valid apart from the model > changes. My > guess is that 1.5 will invalidate a bit more, but not too > much. Mostly > the part about page mounting and nice URLs will change. The > internal > request processing implementation is completely rewritten, > but that > should be transparent to the most of us (and was not > covered in the > book). The same goes for Wicket Ajax: completely > rewritten, > transparent for most users. > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
