I've needed this, too. You should be able to implement it with an interceptor. Apply the interceptor globally to all your actions. If the current action has a "private" parameter, the interceptor can verify that it's being entered a second time (i.e., the first time was through a public action which chained to this private action).
Bob On 9/6/06, Hubert Rabago <[EMAIL PROTECTED]> wrote:
I'm not sure it's a common enough need to justify being built into the core. For something like this, I'd be content with an app-specific extension and using <set-property> to mark private actions. On 9/6/06, Paul Benedict <[EMAIL PROTECTED]> wrote: > For a lack of a better subject line. Let me explain. > > I have some actions which are not supposed to be accessed by users. They > are mostly for internal uses within the program. Specifically, I like to > include many actions on a page and build a poor-man's portlet. So what I > have, architecturally speaking, is one action whose view triggers a > whole bunch of other actions. > > My thoughts lead me to this: while it is very low probability that these > included action paths can be guessed at, I nevertheless do not enjoy it > being above zero. > > I propose adding a new attribute which dictates when an action may be > invoked. I do not have a favorite choice among my ideas, but here they are: > 1) A public attribute; defaults to true. > 2) A private attribute; defaults to false. > 3) A dispatcher attribute; defaults to all; allows > request|include|forward|error (like the filter dispatcher attribute of > web.xml) > > For my needs, I want to be able to say which action mappings may not be > directly accessed; they must be forwarded to or included by. > > Paul > --------------------------------------------------------------------- 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]
