(nobranch) :  hornetq #notification #api :  Now the jetty connector is used with HornetQ, remove the use of durable subscription as they aren't required by Silverpeas when notifying the Silverpeas objects about some events. As the subscriptions aren't more durable, they are lost once the connection is closed and hence if the JVM aborts for any reasons. In the case a connection is unexpected closed, adds a code to recreate the lost subscriptions with the new connection
hornetq #notification #api :  Merge branch 'master' of github.com:Silverpeas/Silverpeas-Core into hornetq-notification-api
hornetq #notification #api :
In jboss-web.xml, the dependency of the war on the JMS comment topic is replaced by a dependency on the JMS Netty connection factory.
The durable subscriptions are now replaced by a non-durable subscriptions: this approach is more light and suits better our needs.
As subscriptions are no more durable, a subscription recovery mechanism is now performed in the JMS implementation of the Notification API. This mecanism is triggered at connection lost.
Now, two JMS sessions are opened: one for the subscription and another one for the publishing. By this way, it will be more easy latter to improve the scalability by increasing the number of JMS sessions for the subscriptions or for the publishing.
Merge branch 'hornetq-notification-api' of https://github.com/mmoqui/Silverpeas-Core into integration

to integration
starting feature #4277 by changing spaceLook.jsp to be XHTML compliant
Feature #4152 : adding a mechanism to force the user to change its password
Merge branch 'master' into feature-4152
Feature #4152 : refactoring some packages and fixing some unit tests
Feature #4152 : always refreshing the user list into domain content management of back-office
feature #4147 :  Introduces an API in Silverpeas for handling cryptographics functions whatever the security Java library (bouncycastle, java security/cryptography,...) used for the purpose. The existing code about enciphering (yet the Blowfish cipher) has been migrated to satisfy this new API. The old code on the asymmetric cipher is kept in state for the moment; it will satisfy the new API later
feature #4147 :  Now, the old code to encrypt and decrypt digital data by using a PKS infrastructure (CMS or Cryptographic Message Syntax) is based on the new Silverpeas Cryptography API and it is provided as a Cipher implementation to perform PKS#12 and PKS#7 tasks
Feature #4152 : adding the possibility to oblige the user to change his password on his first login
closing main part of feature #4277
on feature #4277, upgrading REST service space-appearance to support new attribute 'css'
Bug #3914 : removing of boring JavaScript message alerts when logging to Silverpeas (under Chrome only).
Take into account some passwords were encrypted with the MD5 hash function (but they shouldn't be so)
feature #4147 :  Add a CAST5 cipher. Now the key passed in the encryption and in the decryption methods of the cipher implementations is an instance of a new class, CipherKey; the CipherKey class wraps the concrete representation of the key (it can be a raw key or one coming from a key file, ...)
Updating Apache Tika
feature #4147 :  Replace the current implementation of the Unix SHA-512-based crypt (coming from the University of Texas, Austin) by the one that uses directly the Crypt class of the Apache Common Codec library.
feature #4147 : Add the following features to the ContentEncryptionService: the encryption and the decryption of contents, whatever they are.
In order to be agnostic about the content type, a content is passed either as a one or more strings, each of them representing a content field/property or as a Map in which each entry is a field/property of the content.
The encryption and the decryption of contents can be also performed by passing as arguments one or more providers of contents. The provider is a way to give to the encryption service several contents to process by loading once the encryption key and the cipher; these contents are processed in flow (a content is taken, processed by the encryption service and then returned updated to the provider).