Andrew Hill wrote:
snip
For the other usage, where people have trouble creating a finely-grained
business API, there's a new Chain package in the Commons sandbox that
can help. This package makes it easy to chain together arbitrary units
of work, so that you can do things like create a move
List
Subject: Re: Action Chaining
It is becoming commonplace to use an Action as a front for a server
page. This is not what people mean when they talk about Action chaining.
Some people start to use the Actions as finely-grained business actions.
For example, they want to accomplish a move
There are probably many different solutions to make action chaining more
intuitive. However, action chaining is not considered a best practice in
the Struts community so effort will not be put forward to make it easier to
do. There has been a lot of discussion of action chaining in both the user
within it, that I'd get better
feedback here.
Thanks,
Derek Richardson
-Original Message-
From: Sgarlata Matt [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 4:05 PM
To: Struts Developers List
Subject: Re: Action Chaining
There are probably many different solutions to make
It is becoming commonplace to use an Action as a front for a server
page. This is not what people mean when they talk about Action chaining.
Some people start to use the Actions as finely-grained business actions.
For example, they want to accomplish a move by forwarding to a
copy Action and
to be used on a subsequent JSP page. I think if we
addressed this, the need for chained Actions would be
greatly reduced.
James
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 10:16 PM
To: Struts Developers List
Subject: Re: Action
Personally, I would tend to use a coarse-grained bean that contained the
properties for both pages.
But, AFAIK, calling RequestUtils.createActionForm directly is
sanctioned, especially as a way of obtaining a DynaActionForm.
-Ted.
James Turner wrote:
I haven't seen anyone mention the most
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 12:26 AM
To: Struts Developers List
Subject: Re: Action chaining: (was - Re: Why are people up on Struts)
On Thu, 12 Dec 2002, Eddie Bush wrote:
:-) Precisely. Everyone
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
So, if we're talking about one ActionMapping forwarding (or
redirecting) to another ActionMapping, then sure. Everything is
above board, and you can follow the bouncing ball through the
Struts Config and see what's
/do/action?dispatch=delete or anything else.
Erik Hatcher wrote:
Thats too tightly coupled for my tastes though. What if I want to put a
delete hyperlink on some other page and have it forward somewhere else?
In your example I don't think you'd have that capability. In my
chaining
LOL - this is getting comical :-) Personally, I chain for the same
reaons that Laird notes. Ex: deleteDetail.do has a success forward to
showDetails.do. Call it illegal, but it works just fine :-) One thing
I do do is always redirect instead of forward -- I can certainly see
where
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
There is no question that there are issues with forwarding with form
population and such [...]
I'm sure it just flew by me in all the email, but where can I look to see
what these issues are? Any good search terms to
Eddie Bush wrote:
Erik Hatcher wrote:
There is no question that there are issues with forwarding with form
population and such, and the known issue with multipart data (which is
an isolated use-case anyway).
The multipart issues exists regardless of whether you are chaining or
not - no?
the same admonishments could be used about writing methods whenever
you're using call-by-reference.
ab
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 2:02 PM
To: Struts Developers List
Subject: Re: Action chaining
Eddie Bush
This has been a fascinating thread to catch up on! ;-) I'm more than a
little surprised, though, that everyone's still in the box on a solution
to Erik's problem.
I have exactly the same scenario that Erik does - basically, you have some
code that deals with the incoming request, and some code
15 matches
Mail list logo
