Comments on From Java to Java EE: Do NOT write books this way! "Wicket in Action" ca...

Unless you're willing to pay for 1000+ page bo...

2011-03-13T18:10:55.439+01:00

Unless you're willing to pay for 1000+ page books, you're going to find a *lot* of stuff is out-of-scope.

Be realistic. Book authors make pennies per hour writing low-volume tech books.

You want more documentation on that stuff? Write a blog post instead of complaining about it, or write your own book. It's a non-trivial undertaking, and there's not enough time, not enough room, not enough reward, etc. to put in everything *you* think should be in.

I also read the book. What I'm missing in it i...

2010-05-09T01:23:20.742+02:00

I also read the book. What I'm missing in it is info about the lifecycle of a Wicket app and requests.
Something that is very important in complex web frameworks like this.

i read that book and it is great, the example is g...

2010-05-07T22:24:31.577+02:00

i read that book and it is great, the example is good and the explanation of the components too.
The book has the minimum to start in wicket, and explanation of the core, components, layout, i18n, forms, validation, Models, url coding, resources, etc.
Wicket framework is really big, if you need to write all in detail, it would be a 1000 pages book.
The only thing wrong i can say about that book, is that is not update with the new release of wicket.
NM

I totally share your frustration with this book. I...

2010-05-07T21:12:25.966+02:00

I totally share your frustration with this book. In fact, it looks like this is a common practice with Manning authors. I too recently bought a copy of The Quick Python Book and was very angry at how many code sample and design decision were not explained.

I've giving up on Manning books; they're all crap.