Feature #907 : subscribing to a suggestion box component.
feature #907 sprint4 :
* by default, a suggestion has no validation object set. This property is set only when requested (during the first validation of the suggestion). This property can be
then updated for further validation (after a refusal). This characteristic is taken into account in the tests.
* update the signature of SuggestionBox$Suggestions#validate: it accepts now the ContributionValidation instance as a second argument. This one gives the information
about the validation to perform.
* change the property name 'state' in Suggestion by 'status'; 'state' is a reserved SQL-keyword, so the renaming is for avoiding some unexpected problems with
the persistence of suggestions. Tests are updated to take into account this change as well the SQL instructions to create the tables for the Suggestion Box application.
feature #907 sprint4 :   Render the attachment pane: both the suggestion author and the validators can manage attachments to a given suggestion in pending
Feature #907 : integrating Aurore's work around the homepage of a suggestion box.
(modifying findNotPublished in findInDraft for a user)
(adding findOutOfDraft for a user)
(adding a criteria to manage the WYSIWYG content loading for a suggestion)
(adding the remove of subscriptions related to a complete deletion of a suggestion box component)
Feature #907 : refactoring
(get back Transaction mechanism introduced by Miguel to handled the finest as possible the JPA transaction into a service)
(moving user notification sending from SuggestionBox.Suggestions to SuggestionBoxService)
(moving the specific status information of suggestion to the ContributionValidation that is a common object)
Feature #907 : fixing an error
feature #907 sprint4 :   Now, the participant of a suggestion box can comment the suggestions of others and of him. The readers can only see them.
Feature #907 : fixing display attachments for validated suggestions
(refactoring back Transaction mechanism introduced by Miguel to handled the finest as possible the JPA transaction into a service)
Feature #907 : splitting of the suggestion page into two ones -> one for the read only mode and an other one for the edition mode
feature #907 sprint4 :   Register the application Suggestion Box among the UserCommentNotificationService so that the concerned users can be notified when a comment is added to a suggestion
Feature #907 : handling the case of the suggestion box is public
feature #907 sprint4 :   Add a new page to render all of the published suggestions. In this page, the suggestions will be paginated and can be sorted by the user according to some suggestion properties. Laters will be done later
feature #907 sprint4 :   Refactor Suggestion.get javascript method so that it accepts now just an identifier instead of just an array. Code the back button in HTML page to go back to the last page
feature #907 sprint4 :   Refactor the get() method of the Suggestion javascript service by accepting now either an identifier (Published, a suggestion identifier, etc.) or an identifier following by some criteria to filter the asked suggestions. Supports now the pagination of the published suggestions (in the list of published suggestions); the pagination is performed for instance in the web layer once all the suggestions are retreived and cached for the current user
feature #907 sprint4 :   Now the published suggestions per user cache is managed by the Silverpeas Cache Service API. For instance, the value set in the cache is a concurrent map in which is registered for each user the sorted and published suggestions to render to the user
Feature #907 : integrating Aurore's work around suggestion page (view and edit) and suggestion list page.
(upgrading angularjs and associated plugin sanitize)
(adding the getting of uploaded file from the HttpRequest)