Eelco,
I am reading the PDF version of the book called Enjoy
Web Development with Wicket. Basically it is a good
one with many interesting examples, but these examples
are simple and keep me wondering whether Wicket can
handle other more complicated situations.
I feel this book does a good
How is your Wicket in Action?
Download the first chapter and see for yourself :-) It's free after
all, and no registration required (I think).
Eelco
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
1. It is too much coding. Anybody used Valang in
Spring Module? By using Valang, the validation code is
much clean and a lot fewer and you dont need to create
a class simply for this simple validation.
The example you quoted is an example of a reusable validator that
checks the values of
Eelco,
Thanks so much for your input! I am still seriously
learning Wicket now and will see if I will change my
mind.
BTW, what is the best Wicket example website? I often
have many questions when reading tutorials with simple
examples. I wonder Wicket can do or how do more
callenging/complex
Thanks so much for your input! I am still seriously
learning Wicket now and will see if I will change my
mind.
BTW, what is the best Wicket example website?
Best to download the Wicket examples distribution or check out from
our subversion repo, so that you can browse through the source.
I am migrating from JSP+Valang+...+SpringMVC to Wicket
and am also still evaluting it. So far so good until I
saw this instance about using Form Validator to
validate two related form fields.
Problem (p81-82, book Enjoy Web Development with
Wicket, PDF version only):
Suppose a postage
On Fri, May 02, 2008 at 07:25:01AM -0700, David Chang wrote:
I have the bad feeling about this way of validation
1. It is too much coding. Anybody used Valang in
Spring Module? By using Valang, the validation code is
much clean and a lot fewer and you dont need to create
a class simply
don't agree at all of course. ;-) and i'm going to give you about the same
stock answer i always give: if you're repeating yourself, stop doing that.
writing redundant form code? writing redundant validators? think. use OO
design patterns. it's amazing what you can do with objects. at
The problem is that with declarative approaches,
once you step outside of the use-cases envisioned by
the designer of the declarative system things become
much more difficult.
I would like to think practical. How many such
unexpected situations would happen? Besides, you can
always code extra
auto-generation of anything is a horrible idea. it's a computer-driven
violation of the DRY principle and you'll get what you deserve. there are
pretty much always smarter approaches than code generation.
you ought to be able to use wicket to create a constraint driven validation
system that
On Fri, May 02, 2008 at 09:13:40AM -0700, David Chang wrote:
Weird. Your experience is exactly opposite to mine.
I found Spring MVC to be hopelessly scattered:
declarations in XML, controller code in Java, view
code in templates.
I dont have any real experience yet. It is mere my
11 matches
Mail list logo
