Dale Newfield wrote:
Gena Batsyan wrote:
As I said, if using chain, the whole load of parameters is applied to
the second action, which I want to avoid, I want it to get nothing
except of what I'm explicitly define.
It sounds like you're trying to use the wrong tools. You're looking
for a way to trigger the creation of an object, but you don't want to
let the browser know that an action that does this exists, and you
don't want to allow any other than a specific few parameters to get to
that action. Then why does it need to be a (web layer) struts action?
Sounds like it should be a method call in a manager class. The action
from which you're trying to chain should really just be collecting all
the bits you approve of and making a method call.
Why not, we have two actions with absolutely distinct purposes, one for
entry creation and another for entity listing, but the listing has a
little feature to display messages.
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
