You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/05/02 07:57:05 UTC

[jira] Updated: (WW-1805) Apply "convention over configuration" principles to default interceptor and result name

     [ https://issues.apache.org/struts/browse/WW-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown updated WW-1805:
--------------------------

    Fix Version/s:     (was: 2.1.3)
                   Future

> Apply "convention over configuration" principles to default interceptor and result name
> ---------------------------------------------------------------------------------------
>
>                 Key: WW-1805
>                 URL: https://issues.apache.org/struts/browse/WW-1805
>             Project: Struts 2
>          Issue Type: Improvement
>            Reporter: Ted Husted
>             Fix For: Future
>
>
> In WW-1707, we offered a consistent set of "camelCase" names for the interceptors and results. 
> In almost all cases, the interceptor/result name matches the Java class name. 
> Rather than introduce arbitrary exceptions, we should rename either the elements or Java classes, so that there is a 1:1 "convention over configuration" correspondence. As a pattern, we could drop the "Servlet" or "Struts" prefix and "Result" or "Interceptor" suffix, or move the classes to a Result or Interceptor package
> The elements or classes that would need to be renamed are 
> * chain / ActionChainResult
> * externalRef / ExternalReferencesInterceptor
> * execAndWait / ExecuteAndWaitInterceptor
> * exception / ExceptionMappingInterceptor
> * params / ParametersInterceptor
> * staticParams / StaticParametersInterceptor
> * sessionAutowiring / SessionContextAutowiringInterceptor
> * tokenSession /. TokenSessionStoreInterceptor
> * workflow / DefaultWorkflowInterceptor
> * store / MessageStoreInterceptor
> * profiling / ProfilingActivationInterceptor
> Of course, the prior names can be supported on an interim basis to ease migration. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.