you can't keep hard (must be transient) references to those resources so you always should be able to look it up again. by, for example, some id that isn't transient
johan On 10/24/07, WicketKeeper <[EMAIL PROTECTED]> wrote: > > > Hi > > I'm new to Wicket to this might be an ultra-dum question :) > > I'm creating a wicket application that gets its data from an online > resource. The connection logic to that resource is in an external jar and > most of those classes don't implement Serializable. Fore ease of > explanation, let's call the entry class for the connection "DataConn". So > whenever I want to get specific data to, say, fill in an > AutoCompleteTextField all i do is list=dataconn.getStuff(). > > Moreover, whenever someone comes to the application's homepage they shoult > only ever have ONE instance of DataConn, i.e. 1 instance for each "user". > > So my question is - what's the best way to go about doing this in Wicket? > I > am aware of Session and Models in wicket (though my understanding is poor) > - > could anyone direct me to the appropriate examples or suggestions please? > > Thanks > WK. > -- > View this message in context: > http://www.nabble.com/Non-serializable-objects-and-efficiency-tf4684047.html#a13384755 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
