which provides the underlying API.
Donnie
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 10:38 PM
To: Struts Developers List
Subject: Re: Multiple controller servlets
These wouldn't exist as such on the ActionResource interface I
suggested
Donnie Hale wrote:
Re: the proposed interface - I'd like to see one, perhaps a base interface
for what you're proposing, which has access to everything for which the
current request isn't needed. And that's most of those elements. That way
all Struts elements that need the non-request-based
would need changed. Is that right?
Any other input?
Thanks,
Donnie
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 7:04 AM
To: Struts Developers List
Subject: Re: Multiple controller servlets
Donnie Hale wrote:
Re: the proposed interface
I had originally thought we might start posting an ActionResources
object in the request, so it would be there when we started to refactor
the tag extensions, and also for the use of other presentation systems
like Velocity templates. So, for a time, it would really be redundant,
and could just
Subject: Re: Multiple controller servlets
Donnie Hale wrote:
Re: the proposed interface - I'd like to see one, perhaps a base interface
for what you're proposing, which has access to everything for which the
current request isn't needed. And that's most of those elements. That way
all Struts
These wouldn't exist as such on the ActionResource interface I
suggested. These are really just shortcuts to the API for the underlying
resources, like
formBeans.addFormBean(formBean);
So, if someone wanted to do them through an ActionResources object, they
could do the same thing
Do any multi-threading wizards out there have an opinion on
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2214
At the moment, the 'getActionInstanceLock' method returns an object for the
action class to ensure that there is effectively one monitor (lock object)
for each action class.
PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Sunday, December 02, 2001 11:18 PM
Subject: Re: Multiple controller servlets
Do any multi-threading wizards out there have an opinion on
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2214
At the moment
-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 02, 2001 4:52 PM
To: Struts Developers List
Subject: Re: Multiple controller servlets
Under the heading A step in the right direction, how about if we
(meaning I) were to start with defining a simple ActionResources class
I could be convinced that we can refactor 1.0.x for multiple servlets,
as you originally described, and continue the work in 1.1 (more likely
1.2) to switch over everything over to a JavaBean. In terms of
progressive refinement, it may make the most sense to expose the
ActionServlet first, and
Is there anything wrong with having a given ActionServlet save itself in
the request at process() time and then have all attributes that are
currently accessed through application scope can instead be accessed
through the servlet that has been saved in the request? That way all
components are
I haven't studied the source from this perspective, but it certainly
seems feasible.
I don't know if we want to expose the ActionServlet in the request as
much as the resources associated with it. So I'd think about an
interface for a JavaBean that encapsulated the Mappings and the Messages
and
: Re: Multiple controller servlets
I haven't studied the source from this perspective, but it certainly
seems feasible.
I don't know if we want to expose the ActionServlet in the request as
much as the resources associated with it. So I'd think about an
interface for a JavaBean that encapsulated
We just changed the ActionForm to use a wrapper object, rather than the
original, since exposing the ActionServlet this way can be exploited.
I'm just thinking that many of the components that we use may have wider
user, and we should avoid binding things to the ActionServlet class.
Avoding
.
[EMAIL PROTECTED] wrote:
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, November 14, 2001 2:18 PM
Subject: Re: Multiple controller servlets
A fix for multiple struts-config has come along first, but the need
)
Ted Husted [EMAIL PROTECTED] on 11/15/2001 09:58:00 AM
Please respond to Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
cc:
Subject: Re: Multiple controller servlets
Of course, I fully expect to see responses saying both. ;-) I guess my
question
I would like some feedback on the subject of multiple controller servlets.
I have seen some of the previous discussion in the archives. The basic
problem has to do with modularity - both in the runtime and at development
time. The current solution of multiple config files certainly solves
. The helpers
could then use the key to retrieve the configuration from the
Collection.
-Ted.
Tim W Wilson wrote:
I would like some feedback on the subject of multiple controller servlets.
I have seen some of the previous discussion in the archives. The basic
problem has to do with modularity - both
- Original Message -
From: Ted Husted [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent: Wednesday, November 14, 2001 2:18 PM
Subject: Re: Multiple controller servlets
A fix for multiple struts-config has come along first, but the need for
multiple resource files
19 matches
Mail list logo
