- Series: In Action
- Paperback: 392 pages
- Publisher: Manning Publications; 1 edition (September 12, 2008)
- Language: English
- ISBN-10: 1932394982
- ISBN-13: 978-1932394986
- Product Dimensions: 7.4 x 0.8 x 9.2 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 19 customer reviews
- Amazon Best Sellers Rank: #1,256,404 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Wicket in Action 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
About the Author
Martijn Dashorst is a software engineer with over 10 years of experience in software development. He has been actively involved in the Wicket project since it was open sourced, and has presented Wicket as a speaker at numerous conferences, including JavaOne and JavaPolis.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
For me it is also a big plus this book is about Wicket, not about everything that Wicket is even remotely related to (like half of the book for ORM libraries; such topics -- ORM, DI, testing -- are touched, but that's it). On the downside several core Wicket issues are also lightly touched or not mentioned at all. Namely -- let's start from minor topics:
* overview of MVC vs. Wicket is cut off -- MVC it just described and instead of comparison it ends up with sudden conclusion Wicket is better; reader interested in design of frameworks will be really disappointed (I am)
* "dynamic" page (hiding/showing part of it) is presented using Ajax -- what about pure JS, because Ajax seems like overkill
* Ajax calling -- on-error handling is just mentioned, on-submit is probably not mentioned (because it is described as submit-completed event; p.253)
* differences between Wicket links are not fully explained -- I rather guess, than rely on what I've read
* I didn't see how you can customize URL composing -- Wicket by default creates some scary ones, and the first you would probably like to do is to make them user-readable
* a nasty mistake is using plain passwords in authentication chapter -- I know, the books serves rather as an example, but even examples should not teach bad habits
Adding to this few mistakes like stating that "we are extending Stateless form to make page stateful" (p.271) does not change my opinion about this book. It is hard to be perfect. However more serious problems exist too.
The authors spend a lot of time (too much for my taste) for introductions, summaries, lengthy analogies. Let's say you have a chapter titled "Authorization". Is this really necessary to explain to reader that this chapter will be about (... I feel your excitement ...) authorization (who would guess, ha?). Come on... half of the page (or more)? This is especially annoying, when you face the publisher rip-off, but we come to that.
So for introductions to introductions there was space, but for adding chapter about web service (is Wicket suitable to build one? or use one? how?), data validation (the authors describe the validation is performed by Wicket, but crucial point is -- on which side? client? server? or both?) there was no space. There was no space for very basic thing -- thoroughly explaining how to setup WWW server with Wicket (emphasis on "thoroughly").
This ends up my review about the content as information -- for this I can give 4/5. There 3 things more to cover though -- the longer you read, more tired you get. Despite every -- even free -- editor has now syntax highlighting, such invention somehow was missed by publisher, so all code is printed in plain same font (Courier?) -- no matter if it is a keyword or not. Authors do not help in this department either -- instead of building code piece by piece, which is very desired when explaining anything, they go with on-fly class constructing (guys, the fact the feature exists in the language does not mean you have to use it). As the result you are struggling with dissecting a method which creates on-fly a class, which has method, which creates on-fly a class which has a method... OMG. Great for mind puzzle, quite contrary if you have to understand it, and find that closing brace which matches the one you are looking at.
I hope in second edition we get a class definition, then a class which uses it, then a class... One at a time.
OK, time for really sad part. You are buying a book, once you paid, you own the book. Every page is yours, no matter how often you read it. So you can say, that you have your reading for free (after you already spent the money). And here Manning comes with revelation -- you have ADDITIONAL chapter for free (actually it is not additional chapter -- setup -- it is essential part of the book, it was simply removed from the printed book). The chapter you would normally think it is already there, because you -- as I said -- paid for it. But you see, printing books is expensive business, and Manning figured it out how to cut the costs. Instead of printing it, they make you to download it. Now, in order to read the book, you have to print the chapter by yourself, or keep ebook-reader next to the book, in order to read whole content. If you don't get the scheme Manning pulled out here, here is the analogy -- you bought Encyclopedia Britannica, but after purchase you found out B- and C- entries are not printed, you have to download them and use them as an ebook. "FOR FREE", you see.
THIS IS FRAUD, THIS IS STEALING. PUBLISHER (MANNING) CHEATS. Since the review is for the book as a whole piece -- 3/5. Idea that I print additional chapter, and glue it somehow to the book, to make it look like A-Z guide, is ridiculous (especially considering I paid for the book, not for DIY, I want-to-be-a-publisher toy).
I've been brushing up on my Wicket and wanting to get back up to speed on it after a 2 year break and knew about Wicket in Action -- I was specifically nervous about picking up a book that only covered Wicket 1.3 and 1.4, with 1.5 having been out for a while now and future versions coming out all the time. I was really hung up on not getting old material so I wouldn't "learn the wrong/unoptimized way" of doing stuff.
Suffice it to say, I finally got the book and love it -- Wicket is such a mature project, that a good 65% of the book is covering core/fundamental Wicket stuff that will apply no matter what version you are using (assuming 2.0 isn't some rewrite).
Not only that but the authors are really excellent writers. They have a light hearted way about them that make the reading easy, logical and perfectly descript to understand their points without reading and re-reading paragraphs.
I'm enjoying reading this book quite a bit and highly recommend it to anyone interested in Wicket. The online forums and tutorials are excellent supplemental information -- but this book gives you the whole genesis story of Wicket... why it was created, what problem it solves, why parts of it are designed the way they are and so on.
I've been hung up on 'Models' in Wicket for about 2 years now and I finally realized why the other night -- I've always assumed that the *model* was a storage of information, in the classic sense... last night in Chapter 3 it clarifies "The model can really be though of more as a PROXY, or an object that knows how to GET you the data for the component".
Once I read that, all this "PropertyModel" and "CompoundPropertyModel" stuff made WAYYY more sense to me.
There's a very good chance I'm functionally retarded, but I still found that clarification hugely helpful for my mental map... others may as well.
Overall an excellent book, pick up a copy if you are on the fence and if you are worry about learning "outdated material", don't. There is so much core stuff in here, even covering the newer AJAX functionality, that it's all pretty much applicable even for Wicket 1.5/1.6
Most recent customer reviews
"Wicket in Action" is a guide on building web applications with Wicket framework, which is very fresh and...Read more