Re: [Wicket-user] Component should never pass in null to model.getObject(), how else to get a reference to Application within a Model that could be detached within a clustered environment?

2006-12-17 Thread Johan Compagner
We can't give a object to that model at that point. Because those are really 2 different things! If we would give the object to it then we wouldn't get the root object. But it would try to get a property of the object and try to evaluate that one. In 2.0 that component param is even completely

Re: [Wicket-user] Component should never pass in null to model.getObject(), how else to get a reference to Application within a Model that could be detached within a clustered environment?

2006-12-17 Thread Erik van Oosten
You can get the current application with Application.get(). Similarly, you can also get the current Session with Session.get(). As you found out yourself, you should never ever hold on to a reference to the Wicket Application. Before you know it it is serialized into a replicated session.

[Wicket-user] Component should never pass in null to model.getObject(), how else to get a reference to Application within a Model that could be detached within a clustered environment?

2006-12-16 Thread David Berkman
Component currently has this behavior. /** * Gets the backing model object; this is shorthand for * getModel().getObject(). * * @return The backing model object */ public final Object