To improve the ability of users to select which pieces of Shale functionality they wish to use, split the following functional subsets out of shale-core into their own (new) modules:
* shale-application -- Application controller features
* shale-validator -- Integration with Commons Validator
To improve the ability of users to select which pieces of Shale functionality they wish to use, split the following functional subsets out of shale-core into their own (new) modules:
* shale-application -- Application controller features
* shale-validator -- Integration with Commons Validator
* shale-view -- View controller, exception handling, application callbacks
First step at refactoring the functionality of shale-core, pulling out
all of the view controller functionality. As of this change, web
applications wanting to use this feature should make two changes:
* Add a dependency on shale-view-xxx.jar. For Maven2 users, that
means adding the following dependency:
* If you are using the <s:subview> tag in JSP pages, declare a new
tag library, and switch to the new (vc:) version of the subview tag.
The new taglib declaration you need is:
Clean up APIs (plus some checkstyle warnings) after separating the shale-view
module out of the core library. Migrate a couple of constants from
FacesContstants (internal implementation) to Constants (available for
application use).
Factor Commons Validator support out of shale-core into a new module
"shale-validator". We do not yet have any example or test applications
using this code, so we cannot yet verify correct operation. In addition,
the current implementation uses JSP tags with behavior in some cases,
which will cause integration difficulties with non-JSP view handler
implementations such as Clay and Facelets.
Add an exclusion for xml-apis to the shale-validator POM, so that all
downstream users will receive it. Remove the explicit dependency on
Commons Validator in shale-usecases, because the correct dependencies
are now getting transitively inherited.
Move a forgotten resource file from shale-core to shale-application. Also,
remove from it the intialization and cleanup of the original dialog
implementation, because that has now been farmed out to shale-dialog.
Task
Resolved
Major
Refactor functionality from shale-core into separate modules
