Andrew Hill wrote:
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" command
ined DOM decorators.
Heres an example that does a listview table thingy:
Of course for an action step sequence the steps could do such things as
"copy" or "delete".
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Saturday, 27 September 2003 1
most common use of Action
chaining, which is to process the form values from a submit,
and use them to prepopulate a second page. Currently, this
requires two Actions because there is no officially
sanctioned method of instantiating a new form from an Action
to be used on a subsequent JSP page. I thi
I haven't seen anyone mention the most common use of Action
chaining, which is to process the form values from a submit,
and use them to prepopulate a second page. Currently, this
requires two Actions because there is no officially
sanctioned method of instantiating a new form from an Acti
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 fo
I was trying to avoid rehashing old arguments about action chaining. I have heard two
arguments: one, it is not supported and can cause strange results and, two, it is
indicative of bad design (the argument made below).
I disagree that action chaining is always indicative of bad design. See my
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
To enable action chaining in an intuitive way, it seems that when the ActionServlet is
called, it can look for an attribute in the request that indicates whether it has run
before in this request. If the attribute is not there, do everthing and then set the
attribute; if the attribute is there
gzilla/show_bug.cgi?id=21949
Multiple Modules : Action Chaining with ForwardAction gives 404 error
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
gzilla/show_bug.cgi?id=21949
Multiple Modules : Action Chaining with ForwardAction gives 404 error
Summary: Multiple Modules : Action Chaining with ForwardAction
gives 404 error
Product: Struts
Version: 1.1 Final
Platform: Other
OS/V
There is a new URL for my Struts Action Chaining package.
http://www.strutschaining.org/
Thanks for all of your feedback!
Karl
- Original Message -
From: "Karl Baum" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Monday, De
Some time ago I emailed the developers list with the idea of an Action which
chained other Action's together based on Locale. I have implemented the
idea and posted the results on the web along with some documentation:
http://kbaum.freewebsitehosting.com/doc/
Please take a look and let me know w
> -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 Bu
ward(someComputedString) call.
> But, then there's Action chaining. Here, people have an Action
> class create an ActionForward on the fly, jam in some parameters,
> and toss it back to the controller. This is where Action classes
> start binding to Action classes, and the mud
can to minimize the impact of one upon the other. If
> >something is clear, i.e. the shape of the buttons is presentation layer,
> >the layout of the tables is business layer, you put it in the correct
> >space. If something is gray, i.e. frobnicatation, you understand it the
> &
ng request, and some code that deals with
preparing to present the next page, and you want to decouple those. One
solution, which is where this thread started, is action chaining, but we
know there are issues with that.
A much cleaner solution involves just a little thinking outside the box.
Well, there's Action chaining, and there's action chaining. It's a
perfectly valid idea for an ActionMapping to select where control
should go next, as Erik is doing. It's fundamental to the
architechtural, and instrumental to how ActionForm validation
works.
So, if we&
Matt Raible wrote:
I can't help chiming in as I'm in the midst of writing an example
application using Struts for a Wrox book (Professional JSP 2.0). On my
last Struts application, I used LookupDispatchAction's for all my
actions. I basically organized it by entities, so that I had a
UserAct
If you say it this way then... this is what I do, in case I did not make
it clear:
I have a baseAction (of course).
The concrete actions, for example UserAction has {
onDelete(){}
onSave(){}
onDisplayList() {}
onInsert() {}
}
The baseAction dispatches execute event.
In some cases those events go
Naw - I think what he's saying is that, like you'd have a showUsers
which would populate a userForm, then you'd have, say ... createUser,
readUser, updateUser, deleteUser. Your deleteUser would then chain back
to showUsers so the list could be viewed again. At least ... I think
that's kind of
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 wrote:
Erik Hatcher wrote:
There is no question that there are issues with forwarding
w
stuff seems a little dramatic. it
seems 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: S
ing avoids this issue altogether by causing another request to
be created.
We're talking a little non-sequitor here. Action chaining in no way is
tied to whether I'm doing redirects or server-side forwards - either are
possible with them.
But you are absolutely correct about these issu
Phase Web and Multimedia wrote:
I see my world breaking into a few pieces
MODEL | LOGIC | VIEW LOGIC | CONTROLLER | VIEW
So, in this we all get the lines blurred. I believe that the struts
framework has it's way of handling all of this. But, action chaining is not
one of them "by de
I see my world breaking into a few pieces
MODEL | LOGIC | VIEW LOGIC | CONTROLLER | VIEW
So, in this we all get the lines blurred. I believe that the struts
framework has it's way of handling all of this. But, action chaining is not
one of them "by design". I'm not say
I've managed to avoid Action Chaining all together.
I worked recently with a company that has a framework they wrote that uses
"processing pipelines" similar to cocoon. Having been a struts guy for 1 1/2
years now it was a little strange to put my mind on that track. But there
imp
s this and I see how others are
accomplishing the things I use it for without the use of action chaining.
Also, I use redirects also when it is appropriate - which is probably
an example of where Vic's method breaks down since he's relying on the
view data after a delete be in the sa
> -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 t
handy and clean way
to do things rather than dismiss it altogether. I'm keeping an open
mind here as we discuss this and I see how others are accomplishing the
things I use it for without the use of action chaining.
Also, I use redirects also when it is appropriate - which is probab
V. Cekvenich wrote:
/do/action?dispatch=delete or anything else.
Yeah, I get that for the case where I want to delete and return to the
list view. But how about a case where have some other page that wants a
delete link to delete an item, but then return back to that same page?
You'd have t
mething is gray, i.e. frobnicatation, you understand it the
best you can and break it up in a logical way.
Lastly you use the tools available, with action chaining being one of
the tools, to implement your analysis. If your analysis works best with
action chaining, you are a winner, if it works without i
tools available, with action chaining being one of
the tools, to implement your analysis. If your analysis works best with
action chaining, you are a winner, if it works without it, great too.
Edgar :-)
-Original Message-
From: Nelson, Laird [mailto:[EMAIL PROTECTED]]
Sent: Thu
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 forwardi
business facade. When someone starts nesting or chaining actions,
it's an indicate that the actions are being used to implement the
facade.
But what if the chaining is to accomplish something that is entirely
presentation-layer specific? I've always wondered about stuff like this.
Mo
y, onDefault, etc. on set of
actions that relate to he JSP.
So in onDelete(EventObj event) I do this
{
..
bean.delete();
onDisplay(event); // on display does bean.find()
}
hth, .V
Erik Hatcher wrote:
Ted Husted wrote:
Struts is not very powerful. There's no action chaining; all of
> facade.
But what if the chaining is to accomplish something that is entirely
presentation-layer specific? I've always wondered about stuff like this.
Most of the Action chaining I've implemented is because the pages that
assemble an ActionForm don't collect all its infor
Ted Husted wrote:
IMHO, the Actions shouldn't be doing anything except calling
business methods. So, instead of chaining to a DeleteAction, *any*
action should be able call the delete method of the business
facade.
My actions *only* call business methods. I'm chaining "away" from the
Delete
lete(EventObj event) I do this
{
..
bean.delete();
onDisplay(event); // on display does bean.find()
}
hth, .V
Erik Hatcher wrote:
Ted Husted wrote:
Struts is not very powerful. There's no action chaining; all of
the models are one layer deep. Talking with a Struts user, I was
remind
:
Struts is not very powerful. There's no action chaining; all of
the models are one layer deep. Talking with a Struts user, I was
reminded of the ability of an action to forward to another action, and
it's easier than I thought. Silly rabbit. :)
'nuff said.
Although, I&#x
y actions that only do one single thing and then glue
them
>together in struts-config is something I find very helpful.
>
>Is there a cleaner way to do this without action chaining?
IMHO, the Actions shouldn't be doing anything except calling
business methods. So, instead of chain
Ted Husted wrote:
Struts is not very powerful. There's no action chaining; all of
the models are one layer deep. Talking with a Struts user, I was
reminded of the ability of an action to forward to another action,
and it's easier than I thought. Silly rabbit. :)
'nuff said.
41 matches
Mail list logo
