Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
The following page has been changed by TedHusted: http://wiki.apache.org/struts/StrutsActionRelease200 The comment on the change is: Catagorize issues ------------------------------------------------------------------------------ == New Features Under Consideration == - This initial list of new features is taken from the RoughSpots page. + This initial list of new features is taken from the [http://wiki.apache.org/struts/RoughSpots SAF2 Rough Spots] page. + + Review and Refinement * Separate classes that most applications need to use. Isolate classes that the framework uses internally or that are rarely used by applications. (See Rough Spot #3.) * Distinguish between the published public versus private APIs. (See Rough Spot #4.) + * Utilize properties (methods) instead of protected or public fields (). (See #13.0 + * Review exception handling. Some are still being swallowed rather than rethrown. (See #20.) + + Modifications + + * Simplify Text``Provider. (See #15.) + * Modify `ParametersInterceptor` to sort parameter names by depth (using bucket sort) and then map them in that order (shallowest first). (See #21.) + * Use the strategy pattern to swap in different implementations of interfaces like Validation``Aware. (See Tim, NTH #1.) + + [http://issues.apache.org/struts/browse/WW-1343 Deprecations and Removals] + * Deprecate or remove the Around``Interceptor. (See #7.) - * Utilize properties (methods) instead of protected or public fields (). (See #13.0 - * Simplify Text``Provider. (See #15.) + * Eliminate "do" clause for Action alias lookups. Scan Actions at load time for known aliases, and fail fast. + + OGNL + * On the OGNL value stack, rename #request for request parameters and #requestAttributes for request attributes. (See #17.) - * Eliminate "do" clause for Action alias lookups. Scan Actions at load time for known aliases, and fail fast. - * Review exception handling. Some are still being swallowed rather than rethrown. (See #20.) - * Modify `ParametersInterceptor` to sort parameter names by depth (using bucket sort) and then map them in that order (shallowest first). (See #21.) + * Work with OGNL to add Java 5 support. (See #31.) + * Work with OGNL to make it a clear superset of JSTL. (See Gabe #4.) + + Architecture + + * Address the confusing issue of the validation/workflow lifecycle and different methods. (See Patrick #4.) + + Configuration + * Reduce or eliminate need to use fully-qualified class names, over and over. (See #23.) + * Combine configuration DTDs so that Actions, Messages, and Validators can be defined in a single file. (See Ted, #1.) + * Use values on the stack to override/define configuration options. (See Tim, NTH #3.) - * Work with OGNL to add Java 5 support. (See #31.) - * Address the confusing issue of the validation/workflow lifecycle and different methods. (See Patrick #4.) - * Work with OGNL to make it a clear superset of JSTL. (See Gabe #4.) - * Use the strategy pattern to swap in different implementations of interfaces like Validation``Aware. (See Tim, NTH #1.) - * Extends support on actions in xml (See Tim, NTH #2.) - Other feature suggestions + UI Tags - * Use values on the stack to override/define configuration options. (See Tim, NTH #3.) - * Combine configuration DTDs so that Actions, Messages, and Validators can be defined in a single file. (See Ted, #1.) * Change the default submit method for the form tag from GET to POST (See Ted, #2.) - == SAF1 Features to Implement == + == [http://issues.apache.org/struts/browse/WW-1347 SAF1 Features to Implement] == * Wildcard Action Mappings * DynaForm as Model Object - * Extends for action mappings + * Extends for action mappings (See Tim, NTH #2.) == Outstanding Issue Review ==
