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 that.


On Nov 27, 2009, at 1:16 AM, Igor Vaynberg wrote:

create your own subclass of websession that holds the user and then
anywhere within a wicket request you can get to it via:



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 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 purpose the programmer wanted. It was a void * in C; in
Java it would be an Object reference.

What do you think about adding this to Wicket's Component class, and maybe
even others, like Page, Form, etc.?


Keith R. Bennett
Senior Software Consultant
Linked In: http://www.linkedin.com/in/keithrbennett
Blogs: http://krbtech.wordpress.com, http://keithrbennett.wordpress.com

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to