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 DeleteAction, not to it. DeleteAction chains to the view action in the simple example.
And yes, any action could call the delete method sure. Nothing restricting that from happening in what I'm saying.
Ideally, any chaining or nesting should take place behind a business facade. When someone starts nesting or chaining actions, it's an indicate that the actions are being used to implement the facade.That all sounds fine and well, but lets talk specifics :)
*How* do you do it specifically? Especially given my last post to Vic where I want a delete action to be independently available to be used from any page allowing it to forward to other places if desired which may not be a view.
Now, a lot of people do use actions as a facade. I wrote my first significant Struts application this way. I got it out the door very quickly and it performs very well. But, now, in maintenance mode, I regret that expediency, since it is hard to test and always feels fragile to me.I'm not sure I see what is fragile about how I go about things. My actions are very lightweight and single purpose, and extremely reusable.
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
