What you do should work, or you could just get the request object from the Wicket request and cast it down to HttpServletRequest.
Why do you need to set request attributes? Are you integrating with another technology, like JSPs? Eelco On 5/28/07, Matthieu Casanova <[EMAIL PROTECTED]> wrote: > Hi, I need some request attributes in my page. Those attributes aren't for > session but only for the current request. > To do that I made my own WebRequest that extends ServletWebRequest and > changed the > protected WebRequest newWebRequest(HttpServletRequest > servletRequest) > > of my application to use my request. > But I'm not sure it is the good way to do that. > Is there something better to have attributes with request scope in wicket ? > thanks > > Matthieu > > ------------------------------------------------------------------------- > 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 > > ------------------------------------------------------------------------- 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
