Knowing what my co-workers are like, these are the most important things that I
say to them. So this list is directed towards them in particular.
1. When receiving parameters in a constructor or method, a model (an instance
of IModel) is almost always the right choice instead of a raw model
On Wed, 27 Jul 2011 18:29:22 -0400
Jeremy Thomerson jer...@wickettraining.com wrote:
Hello all,
I'm writing an article for a Java magazine and would like to
include in it a list of ten things every Wicket programmer must
know. Of course, I have my list, but I'd be very curious to see
From my experience, stuff where I screwed up or wasted time:
1. Wicket is a UI framework, delegate as much as possible to your own
neutral code base service and components. Data Models etc. Both Server and
Client Side. Client Side:: Don't wrestle with Grids etc in Wicket; if you
can get away with
Hi Jeremy,
I think the most important things a wicket programmer should know relate
to building their own set of resuable components.Here are my top ten
on that theme:
1. Build a reusable set of components tailored for your business domain.
2. Solve a few problems then push up the
Jeremy,
I just threw together the following, which indicates that at least to
me Models are worth 3 of your 10 items.
1. Most components have a backing object of some sort. This object is
referenced via a Model. Significantly, the type of the component and
the model match (e.g. LabelInteger has
1. How static resources work. For a newcomer this can be
shocking/frustrating.
2. Models are a context that holds a reference to a model.
On Wed, Jul 27, 2011 at 5:21 PM, Scott Swank scott.sw...@gmail.com wrote:
Jeremy,
I just threw together the following, which indicates that at least to
1. Wicket's IOC integrations are really easy to get started with, but there
are some gotchas. Since they inject serializable proxies* *to dependencies
instead of the dependencies themselves, the dependency gets
retrieved/created from Guice/Spring each time a page is deserialized.
Therefore, it's
Hi!
I don't recall who the author is and the page is currently down (500
server error), but
http://www.small-improvements.com/10-things-about-apache-wicket-i-love
is a post I enjoyed reading earlier this year.
Regards,
Bertrand
On 27/07/2011 6:29 PM, Jeremy Thomerson wrote:
Hello all,
My Top 10 (some already mentioned):
1. Use LoadableDetachableModels
2. DefaultModels get detached otherwise you need to detach your model
manually (as Dan mentioned)
3. Setup components to pull in their data and state, typically via
models. This includes pulling in a components
