On 7/6/07, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
The Wicket community is (for now) oriented around IDetachable so it's
easier going that way. And I don't think detaching is a bad way to
work--I use it for everything.
can you also not use idetachable for long conversations? as far as i know
all it is is keeping the session and disconnecting/reconnecting between
requests, so....
public class SessionModel extends AbstractReadOnlyModel {
private final Session session;
//constructor that takes session
Object getObject() {
if (session.isconnected()==false) session.reconnect();
}
void detach() { session.disconnect(); }
}
now the instance of this model defines the conversation scope, pass it
around between pages that need to use the same conversation. or is there
more to it then that?
-igor
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
