Renamed a public service method to getClassificationLevels.
Removed a redundant test method.
Code tidying.
Various internal renames to help readability.
Slight javadoc improvements.
Also some trivial changes like fixing typos and copyright years etc.
Removing warnings from within AuthenticationUtil blocks allows IntelliJ to fold them to Java 8 closure format. (fistpump).
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@100020 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Although the Alfresco server starts fine on my machine, there is a timing/dependency issue which means that on Bamboo, ClassificationServiceImpl.initConfiguredClassificationLevels attempts to use the Alfresco DB before it is fully ready.
This check-in changes the service startup so that instead of using a spring init-method, it uses a LifecycleBean to run the initialisation after the server has fully started up.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@99962 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This check-in adds the basic ClassificationService API, its initial implementation, ClassificationServiceImpl, along with some basic support types such as ClassificationServiceException (for service-specific exceptions) and Configuration.
It also adds unit tests ClassificationServiceImplUnitTest and ConfigurationUnitTest.
The ClassificationService begins our support for ‘Classified Records’, whereby Alfresco content can be given a ClassificationLevel and thereafter will only be accessible to users with the appropriate security clearance.
The vanilla service includes a default set, rm-classification-levels.json (Top Secret etc) which links through to the i18n’d display data via rm-classification.properties in the usual way.
The service is defined in its own spring context file, rm-classified-records-context.xml, as it is distinct from the file plan and should be applicable to content outside that file plan.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@99932 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
If the target directory already exists then the step is passed over.
Also avoid downloading transitive dependencies when getting solr4-config.zip,
as this caused issues on my machine, and the dependencies are not necessary
anyway.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@99837 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
98004: NORWEGIAN (Bokmal): Updated files as per EN-RM-rev97654
98005: RUSSIAN: Updated files as per EN-RM-rev97654
98006: BRAZILIAN PORTUGUESE: Updated files as per EN-RM-rev97654
98007: SIMPLIFIED CHINESE: Updated files as per EN-RM-rev97654
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@98023 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
97717: RM-1651 (Capabilities for Copy to action)
97718: RM-1956 (Create record capability allows user to edit metadata and copy category/folder /record)
97786: RM-1972: Methods with invalid policy are granted access
* invalid policy defintions now throw exception .. previously they just granted!
* invalid capability definitions now throw exception .. previously they abstained with no message
* reference to RM.Write removed and replaced with RM.Create or more appropriate permission check
* adjustments to hold capabilities since they wheren't being exercised as we thought
* ManageAccessRights no longer checks for frozen .. you should be able to manage the permissions of an object if it's frozen and you have the capability
* Unit tests for new code and adjustments
* Tweaks to existing integration tests where required
97788: Attempt to fix failing Unit Tests that are passing locally.
97789: Missed update .. fix build.
97851: i18n changes
97858: GERMAN: Updated files as per EN-RM-rev97654
97860: SPANISH: Updated files as per EN-RM-rev97654
97861: FRENCH: Updated files as per EN-RM-rev97654
97862: ITALIAN: Updated files as per EN-RM-rev97654
97863: JAPANESE: Updated files as per EN-RM-rev97654
97864: DUTCH: Updated files as per EN-RM-rev97654
97945: RM-1956: Create record capability allows user to edit metadata and copy category/folder /record
* fixes issue relating to filing records with only CreateRecord capability
97948: Prevent incompatiable disposition schedules from being linked together
* the unpredicatable behaviour was caused by this incompatibility and the resulting uncertaintity over which level of dispostion would 'win'
* RM-1963: It is not possible to cut off record scheduled for cut off if it's linked to a folder with disposition schedule with cut off step set on folder.
* RM-1962: The disposition schedule steps are not working as expected on a record linked to a folder with disposition schedule on it's own.
97949: RM-1973: Can't add to hold
97950: RM-1959: User can add/remove relationship to/from record he has read-only permissions for
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@97988 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
