> i don't really understand what you're talking about because i don't know
> your
> requirements. but don't forget two things: 1) the primary unit of reuse in
> wicket is the panel and 2) you can put any component (such as a panel) in a
> completely self-contained jar because of packaged resources
i don't really understand what you're talking about because i don't know
your
requirements. but don't forget two things: 1) the primary unit of reuse in
wicket is the panel and 2) you can put any component (such as a panel) in a
completely self-contained jar because of packaged resources. if
sounds to me like what you need is indirection
something like
IComponentFactory { Component newComponent(String id, IModel model); }
then you can configure these in whatever context (in your case spring) and
inject those into pages/panels/etc and let them create children.
this is essentially th
Hi all,
I have just created my first wicket app: a simple JCR (jsr-170) browser/editor
with a tree showing nodes on the left, a
form for editing node properties on the right, and a menu with some actions
(add, delete, save etc.) on top.
All 100% Ajax, it just works!
As a side note: I started fr
