Thank you both for your answers, Jeremy and James.
The data structure I'll use in the real case will be a collection of
objects with
one object for each of the user sessions.
That same object will be accessed only once outside the user session
and then it will be erased. There won't be 2
Firstly I hope you are enjoying building your first Wicket web app.
Is this application scope object immutable? What is the data structure?
IMHO, if it's immutable then it's OK to use composition within your
WebApplication by adding this object as a field within WebApplication.
I would just make
If I understood your use correctly, this approach won't work if there are
two users using the application concurrently - you would overwrite one's
application-scoped object with another Right? There is only one
application per application - not per session.
--
Jeremy Thomerson
