In the data provider, you can do: YourCustomSession.get().getUser().getID(). Then this doesn't have to be serialized with the data provider, granted the cost will be very small.
-- Jeremy Thomerson http://www.wickettraining.com On Mon, Nov 10, 2008 at 3:23 PM, Graeme Knight <[EMAIL PROTECTED]> wrote: > > Hi. > > Just learning about IDataProvider and DataViews. > > I've scoped out the repeaters examples but this may be a little > different... > > If I have a userId (for example stored in the Session) of the user as he is > logged in and I wish to use that userId as a criteria for getting hold of > the correct data using a IDataProvider (for a DataView list), then should I > pass in the userID to the IDataProvider implementation and just store as a > private variable? > > Is there a better way of getting hold of (or passing this) information into > the IDataProvider implementation to limit storage/serialization? > > Many thanks, Graeme. > -- > View this message in context: > http://www.nabble.com/IDataProvider-and-Session-related-data.-tp20428354p20428354.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
