, and
cache it locally.
Martijn
On 9/11/07, Anthony Schexnaildre [EMAIL PROTECTED] wrote:
This makes sense. Where would you stick the user on the
requestcycle?
It's not obvious from the javadocs. Is there a wicket way?
-Anthony
On Sep 11, 2007, at 10:05 AM, Maurice Marrink wrote:
Martijn, you
This makes sense. Where would you stick the user on the requestcycle?
It's not obvious from the javadocs. Is there a wicket way?
-Anthony
On Sep 11, 2007, at 10:05 AM, Maurice Marrink wrote:
Martijn, you are absolutely right, i forgot we moved the user from the
session to the requestcycle.
a getter that uses the
session's username/id to retrieve the user from the database, and
cache it locally.
Martijn
On 9/11/07, Anthony Schexnaildre [EMAIL PROTECTED] wrote:
This makes sense. Where would you stick the user on the
requestcycle?
It's not obvious from the javadocs
, Anthony Schexnaildre [EMAIL PROTECTED] wrote:
I am trying to create a link that will replace one panel with another
on the page. This seems as though it should be an easy task but after
many attempts and searching the net for examples I have yet to get it
working so the replacement can happen more than
I am trying to create a link that will replace one panel with another
on the page. This seems as though it should be an easy task but after
many attempts and searching the net for examples I have yet to get it
working so the replacement can happen more than one without the
component
