Richard,
This is how wrapped models work by design.
They need to know the component they are assigned to to be able to find the
resource bundle.
And the owning component needs to know its parent to be able to look in all
resource locators (component, package, application, ...).
It is the same
2 - If you want to use Wicket *in Scala*, work on a transparent layer that
sits on top of stock Wicket and adds nice features that would be useful to
the Scala crowd.
I'm already writing all my personal Wicket in Scala. Works well.
On Sun, Jan 9, 2011 at 2:16 PM, Jeremy Thomerson
Ok, you need to debug whats in a Model when it is added to
a Component. So, in setModelImpl which is called by the
Component constructor you add code to get the object
out of the Model (if its not null, of course) by calling
model.getObject():
void setModelImpl(IModel? model)
{
if (model
On Sat, Jan 8, 2011 at 7:03 PM, richard emberson richard.ember...@gmail.com
wrote:
Ok, you need to debug whats in a Model when it is added to
a Component. So, in setModelImpl which is called by the
Component constructor you add code to get the object
out of the Model (if its not null, of
On 01/08/2011 05:16 PM, Jeremy Thomerson wrote:
Not all that amazing. This is happening*during construction* which always
leaves objects in fragile states. It's assumed that you can't start
monkeying around with an object's state until construction is completed (and
not expect side
