On Thursday 10 February 2005 17:50, Nathan Bubna wrote:
i only rarely put things directly into the
request myself. i mostly use tools to access my request scoped data.
those are easy enough to keep track of in my toolbox.xml file.
So how do u go on about data that you want to make available
On Fri, 11 Feb 2005 10:15:20 +0200, Markos Charatzas [EMAIL PROTECTED] wrote:
On Thursday 10 February 2005 17:50, Nathan Bubna wrote:
i only rarely put things directly into the
request myself. i mostly use tools to access my request scoped data.
those are easy enough to keep track of in my
Hello Nathan,
Thank you for your prompt and detailed response.
Yeah its true that I use request.setAttribute(destinations, destinations) at
some point before rendering the template so that what is must be causing the
problem.
So...does that mean that I have to keep a record of every possible
Yep, that's sure to be the problem. As for keeping record of
everything you put in the request, i'm not sure what the best way to
do this is. personally, i only rarely put things directly into the
request myself. i mostly use tools to access my request scoped data.
those are easy enough to
the relevant code (in veltools 1.1's StrutsUtils) is doing the following:
resources = (MessageResources) request.getAttribute(bundle +
moduleConfig.getPrefix());
if (resources == null) {
resources = (MessageResources) app.getAttribute(bundle +
