--- Ted Husted [EMAIL PROTECTED] wrote:
The problem is that one developer's litter is another developer's
treasure :)
Right now, a lot of components are already pointing to the components
we've scattered about the contexts. If we just move them into our own
context, then those references
At 7:18 AM -0800 12/3/04, David Graham wrote:
I like the one api bean approach because then you don't have to remember
the names of the objects to lookup in the context. You just remember one
name and get the rest from that bean.
We don't need a migration path if we do this for 2.0, only for the
I agree with everything you wrote, however, what I was specifically
talking about was some sort of storage bean that all the global Struts
components could be stored in, so we don't have all these Struts objects
littering the servlet context. Yes, for each request, a ViewContext
instance
The problem is that one developer's litter is another developer's treasure :)
Right now, a lot of components are already pointing to the components we've
scattered about the contexts. If we just move them into our own context, then
those references would break.
To create a migration path, we'd
The public API bean (where the rubber meets the road) could *not* be stored
in application scope, since some of the Struts resources are request and
session based.
The original idea was the ViewContext (fka ConfigHelper) would be created on a
per-request basis (like a Velocity tool). The
+1 for this
- Original Message -
From: Don Brown [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, December 01, 2004 1:00 AM
Subject: Struts API Bean (was Spring dreaming)
On the topic of a Struts API bean, I completely agree. We should have
one bean
On the topic of a Struts API bean, I completely agree. We should have
one bean, probably actually stored in the servlet context, which
contains references to all the Struts-specific components like
configuration elements and message resources. Now this, and the Spring
topic, do overlap since
On Tue, 30 Nov 2004 16:00:49 -0800, Don Brown [EMAIL PROTECTED] wrote:
On the topic of a Struts API bean, I completely agree. We should have
one bean, probably actually stored in the servlet context, which
contains references to all the Struts-specific components like
configuration elements
