At 4:07 PM -0400 10/29/04, Ted Husted wrote:
That's a good point. Start simply by making ActionContext have
bean properties for the four objects normally passed into execute?
Someone mentioned they were already using an ActionContext in their
own apps. Was it you, Joe?
Yes, we use this as the
On Sat, 30 Oct 2004 08:58:56 -0500, Joe Germuska [EMAIL PROTECTED] wrote:
At 4:07 PM -0400 10/29/04, Ted Husted wrote:
Perhaps it should be based on the Chain Context, which has
implementations for various platforms.
I've thought about this, but I've also had reservations about
separation
On Fri, 29 Oct 2004 11:31:34 -0500, Joe Germuska wrote:
Anyone have strong feelings about the method name? Obviously we
can't use validate.
Are we going to make any API additions in 1.3.x or 1.4.x?
For example, Validate includes a parameter for the ServletRequest. Are we going to
migrate
At 12:50 PM -0400 10/29/04, Ted Husted wrote:
On Fri, 29 Oct 2004 11:31:34 -0500, Joe Germuska wrote:
ÝAnyone have strong feelings about the method name? ÝObviously we
Ýcan't use validate.
Are we going to make any API additions in 1.3.x or 1.4.x?
For example, Validate includes a parameter for
the
That's a good point. Start simply by making ActionContext have
bean properties for the four objects normally passed into execute?
Someone mentioned they were already using an ActionContext in their own apps. Was it
you, Joe?
Perhaps it should be based on the Chain Context, which has
