Rating Service. Now limited to one rating scheme per user per node.

Without an explicit requirement for multiple rating schemes being applied to a node by a user and in order to simplify
the code and ease maintenance, the RatingService now only supports one rating scheme per node per user.
A rating can be applied, removed and a new rating in another scheme applied. But if the first is not removed, an exception will be thrown by the service.

This change was a simple edit in the model with changes to the service implementation and test code.


git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@21585 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Neil McErlean
2010-08-04 07:44:07 +00:00
parent 1dd3aa14f6
commit 40a6a8caf6

View File

@@ -18,7 +18,6 @@
*/ */
package org.alfresco.repo.web.scripts.rating; package org.alfresco.repo.web.scripts.rating;
import org.alfresco.repo.rating.RatingNodePropertiesTest;
import org.alfresco.repo.rating.RatingServiceIntegrationTest; import org.alfresco.repo.rating.RatingServiceIntegrationTest;
import org.junit.runner.RunWith; import org.junit.runner.RunWith;
import org.junit.runners.Suite; import org.junit.runners.Suite;
@@ -33,7 +32,6 @@ import org.junit.runners.Suite;
*/ */
@RunWith(Suite.class) @RunWith(Suite.class)
@Suite.SuiteClasses({ @Suite.SuiteClasses({
RatingNodePropertiesTest.class,
RatingServiceIntegrationTest.class, RatingServiceIntegrationTest.class,
RatingRestApiTest.class RatingRestApiTest.class
}) })