Igor Martijn -
Thanks for all the information. I didn't know about the existence of
metadata in the various classes; that's what I was looking for.
I have a question about the metadata implementation. The javadoc
indicates that the special MetaDataKey approach (rather than using a
All -
I'm coding a Wicket table and would like all the components in the
table to have access to a specific reference.
Another framework I worked with a very long time ago (Vermont Views, I
believe) addressed this by providing a user pointer in the class that
could be used for any
create your own subclass of websession that holds the user and then
anywhere within a wicket request you can get to it via:
((MySession)Session.get()).getUser()
-igor
On Thu, Nov 26, 2009 at 6:20 PM, Keith Bennett keithrbenn...@gmail.com wrote:
All -
I'm coding a Wicket table and would like
Igor -
Thanks for responding.
The User solution would work where all components would share the same
reference, but I need each table would have its own reference.
Also, I was thinking it would be nice for each component to have its
own Object. I realize I could have been clearer about
Adding another reference to component would increase the memory
footprint for all users. You are the first one to ask so there's
little to no demand for it. Wicket already has a default object slot:
the model. If that doesn't solve your problem use the metadata.
Martijn
On Friday, November 27,
datatable.setmetadata(mykey, myobject);
.. somewhere in a component under datatable
public mytype findreference() {
datatable table=findparent(datatable.class);
return table.getmetadata(mykey);
}
-igor
On Thu, Nov 26, 2009 at 11:02 PM, Keith Bennett keithrbenn...@gmail.com wrote:
