Added addtional classes, i.e. PermissionEvaluatorMetadata and PermissionEvaluatorMetadataProvider
Created a branch that allows users to secure services with Spring annotations.  Added changes to security and service addons.  Made security addon a feature and allowed it to be used with GWT.  For the service addon, modified the @RooService annotation to include isAuthorized, authorizedRoles, and usePermissionEvaluator.  Users can specify that SpringRoo add a @PreAuthorized annotation to service methods.  The annotation can include any combination of the following: isAuthorized, hasRole, and hasPermission.  Added PermissionEvaluatorMetadata and PermissionEvaluatorMetadataProvider.  These addtional classes create a PermissionEvaluator and supporting classes as well as an applicationContext-security-permissionEvaluator.xml file.
Added applicationContext-security-permissionEvaluator.xml
ROO-3230: Add method level security to Spring Roo services - Moved PermissionEvaluatorMetadata.java, PermissionEvaluatorMetadataProvider.java, RooPermissionEvaluator.java, and applicationContext-security-permissionEvaluator.xml to addon-security.  It made more sense for them to be part of this addon.  Enhanced the RooService.java annotation and ServiceAnnoationValues.java to include authorizedReadRoles, authorizedCreateOrUpdateRoles, and authorizedDeleteRoles.  User can now specify which roles can use which methods.  More than one role is allowed per method.  However, multiple roles must be added after the service is created by modifying the service interface annotation through a text editor.  When creating the service using the command line, only one role can be specified (at this time).
ROO-3211 - Modify the inheritance chain of activities and views in order to increase flexibility.

Fixed error in ApplicationMasterActivities. Deleted FindAndEditProxy and CreateAndEditProxy.
ROO-3211:Modify the inheritance chain of activities and views in order to increase flexibility.

Fixed issue Editor input.
Modified service commands.  It was not possible to select service, only serviceAll.
ROO-3178: If a user adds a field to an unmanaged edit view, do not add it to the managed edit view.

Modified DetailsView so it matches the behavior of EditView, i.e. if a user adds a field to an unmanaged details view, Roo will not add it to the managed details view.
ROO-3211: Modify the inheritance chain of activities and views in order to increase flexibility.

Changed EditViewImpl, DetailsViewImpl, and ListViewImpl to DesktopEditView, DetailsEditView, and DesktopListView to make the name convention consistent with the rest of the scaffoled appplication.
ROO-3179: Better organize the scaffolded views in a GWT application

Renamed DetailsViewImpl to DesktopDetailsView
ROO-3179: Better organize the scaffolded views in a GWT application

Added DesktopListView and DesktopEditView
ROO-3230: Add method level security to Spring Roo services

Changed annotation from hasRole() && hasPermission() to hasRole() || hasPermission()
ROO-3230: Add method level security to Spring Roo services

Added missing import
ROO-3230: Add method level security to Spring Roo services

Changed && and || to AND and OR in preauthorize annotations
ROO-3211: Modify the inheritance chain of activities and views in order to increase flexibility.

Removed unecessary proxyClass field from EditActivity.xtm
Merge branch 'security-enhancement'

Conflicts:
	addon-gwt/src/main/resources/org/springframework/roo/addon/gwt/scaffold/templates/MobileDetailsView.xtm
ROO-3311:  Provide option for Spring Roo managed XML configuration for Services, Controllers, GWT Locators, etc.

Modified ServiceLayerProvider to include a set method that can be as an
alternative to the autowired field.