imo your best option is to override the newSession method in
Application and use your own custom session as it allows you to get
your objects back without casting, as you would have to with metadata,
and it allows you to do do some detach logic (if you need to).
Alternatively you could use the
shameless plug: http://blog.ehour.nl/index.php/archives/14
:)
Matthieu Casanova wrote:
Hi, I'm not familiar with wicket sessions. I understand that I can
create my own session object that extends the WebSession, and that
will have some fields containing my sessions datas. In that case I
have
you should really create your own session.
Usage of the metadata things should really be avoided for that kind of data.
I almost could say. don't use meta data at all, its a wicket internal thing
to store quickly markers and stuff like that.
johan
On 6/22/07, Matthieu Casanova [EMAIL
2007/6/22, Johan Compagner [EMAIL PROTECTED]:
you should really create your own session.
Usage of the metadata things should really be avoided for that kind of data.
I almost could say. don't use meta data at all, its a wicket internal thing
to store quickly markers and stuff like that.
Like Johan said, the typical case is to provide your own custom
session. You'll have strongly typed variables that way and that's the
whole idea users being able to provide their own in the first place.
Metadata is intended for framework-like use. When you don't know/
don't want to force clients
