We use namespaces when we have an application that runs both as a portlet & as a standalone web application. In the former case the portlet interceptor sits at the top of the stack & the latter is just our standard interceptor stack, and we use namespaces to differentiate action invocations between the 2 types.
Maybe there's a better way to accomplish this, but it's just the way we've always done things. If this were to change, we would have work to do. -- Todd Kofford [email protected] > On Dec 12, 2014, at 1:54 AM, rgm <[email protected]> wrote: > > To me it's valuable for keeping an interceptor stack separate for api > requests. > > /api/v1/people/list > Json result > > Vs > > /listpeople.action > Web / template result >> On Dec 9, 2014 2:52 PM, "Paul Benedict" <[email protected]> wrote: >> >> One concept I never really liked in S2 are namespaces. I never found a good >> reason to logically group actions together with common interceptor setup. >> Rather I always find myself in the situation where the interceptor stack is >> globally set and actions have one-off changes. And I also never liked how >> namespaces limit the scope of result types. >> >> Am I right or is this feature really valuable? >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
