I don't know how WebWork stores it's sessions, but I imagine they do
that just in the HttpSession, right? So all you need then is knowing
what attribute (keys) are being used. You could write a custom Wicket
session that proxies these, such as:
class MySession extends WebSession {
...
public User getUser() {
return
(User)MyRequestCycle.get().getHttpSession().getAttribute("_webwork_user");
}
Sessions in WebWork are stored in the HttpSession like this:
ActionContext.getContext().getSession().put(key, value);
so this should be trivial. Thanks a lot!
I have never needed to override newRequestCycle() in the WebApplication
class before, and it seems getHttpSession() is not available in the
default RequestCycle implementation. How do I get a hold of the
HttpSession object?
-- Edvin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
