(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