So you only need it in the wicket code?
then store it in your custom request cycle
or
request.getRequestParameters().getParamteters().put(xxx,yyy)
johan
On 5/28/07, Matthieu Casanova [EMAIL PROTECTED] wrote:
Hi, no, I'm not integrating with another technology. My problem is that
for each
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
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,
Hi, no, I'm not integrating with another technology. My problem is that for
each request, I get some informations from a server, and I need those
informations in several components to build my page. Those informations
cannot be stored in session because they change at every request, and it is
If you can use PageParameters it would be neat (provide your Page's
constructor with it). Otherwise, you'll have to use Eelco's method and
query the request attributes.
Martijn
On 5/28/07, Matthieu Casanova [EMAIL PROTECTED] wrote:
Hi, no, I'm not integrating with another technology. My problem
I don't think I can use PageParameters, my datas do not come from the client
but from a server (the web server is connected to a server that provides
it's data).
Matthieu
2007/5/28, Martijn Dashorst [EMAIL PROTECTED]:
If you can use PageParameters it would be neat (provide your Page's
* Matthieu Casanova:
I don't think I can use PageParameters, my datas do not come from the client
but from a server (the web server is connected to a server that provides
it's data).
You should consider PageParameters as just a concept in the API.
To produce your own PageParameters from the
