Quoting Jeff Caddel [EMAIL PROTECTED]:
If your application uses WebContext (or one of it's subclasses) as the
Context
object being passed down the chain, you already have access to the request
attributes via the getRequestScope() method. There's also other
Map-returning
methods on
If your application uses WebContext (or one of it's subclasses) as the Context
object being passed down the chain, you already have access to the request
attributes via the getRequestScope() method. There's also other Map-returning
methods on WebContext for lots of other useful stuff (headers,
Quoting Jeff Caddel [EMAIL PROTECTED]:
Any feedback on this Command implementation?
The idea is that as a chain of commands is executing objects get
aggregated into a map. The context holds a reference to the map. At
the tail end of the execution chain, this command places the objects
I'm not a commiter, but the idea sounds reasonable to me. I do something
very similiar in Struts when using Jelly scripts, where I have a struts
action that takes all of the http 'stuff' and puts it into the jelly
context, executes a script and then takes the data from the context and
puts it
Any feedback on this Command implementation?
The idea is that as a chain of commands is executing objects get
aggregated into a map. The context holds a reference to the map. At
the tail end of the execution chain, this command places the objects
from the map into the request as request
