Bug #3529. Ensures the div used to be rendered within a JQuery dialog are unique in a web page that can contain several frames, so that the user zoom behave correctly with Firefox
Fix Bug #3657
Merge branch 'BUG_WF_SEQUENCES' of https://github.com/neoludo/Silverpeas-Core into core-5.10.x
fixing bug #3645
Accented characters must not be removed before Snowball filter
Removing three useless classes
fixing bug #3631
auto-detection of applications main page have been improved
simplifying context information pass to JSP
modified JSP files are now xhtml compliant
fixing bug #3202
modifying simply encoding used to generate workflow models
fixing bug #3089
on client-side, a verification between action name and form name is done
Furthermore, it is possible to create/update an action without specifying a form
fixing bug #3211
HTML layer can be associated to all type of form
fixing bug #3201
It is no more possible to set specific label on input for a given form
Label of folder item is used...
fixing bug #3695
fixing bug #3649
replacing callback mechanism by JMS notification service
now, when a file is deleted, a message is send in the "attachment" topic
sharing service listens this topic
Bug #3323. The bug is hardly reproductible, nevertheless, the JMS topic subscribers and JMS topic publishers close themselves explicitly
Bug #3697. Improve the use of the JMS objects (connections, sessions, ...) by reusing them. Use now the durable subscription instead of simple subscription. Durable subscription are living over connections life

Conflicts:

	lib-core/src/main/java/com/silverpeas/notification/jms/JMSSubscribingService.java
	lib-core/src/main/java/com/silverpeas/notification/jms/ManagedTopicsSubscriber.java
	lib-core/src/main/java/com/silverpeas/notification/jms/access/JMSAccessObject.java
	lib-core/src/main/java/com/silverpeas/notification/jms/access/SilverpeasTopicSubscriber.java
Bug #3697. Add a mechanism of retry with the JMS implementation of the silverpeas notification API in which the connection with JMS is reestablished when it turns out to be broken. The retry mechanism is implemented by an utilitary class com.silverpeas.util.ExecutionAttempts so that is can be reused for any jobs

Conflicts:

	lib-core/src/main/java/com/silverpeas/notification/jms/JMSSubscribingService.java
	lib-core/src/main/java/com/silverpeas/notification/jms/access/JMSAccessObject.java
Bug #3697. Now, all use of JMS other than the Notification API is done through the HornetQ JCA that manages for J2EE/JEE applications the life-cycle of both connections and sessions. The JMS implementation of the Notification API accesses directly the JMS as it manages itself the life-cycle of both connections and sessions.

Conflicts:

	config-core/src/main/config/properties/com/stratelia/webactiv/util/jndi.properties
	lib-core/src/main/java/com/silverpeas/notification/jms/access/JMSAccessObject.java
	lib-core/src/main/java/com/stratelia/webactiv/util/JNDINames.java
Bug #3323. Fix the problem of the non setting of the ExceptionListener: it is now set, ready to be invoked at connection failures to reopen a new connection.
Merge branch 'core-5.10.x' into bug-3649
fixing bug #3649
replacing callback mechanism by JMS notification service
now, when a file is deleted, a message is send in the "attachment" topic
sharing service listens this topic
Merge branch 'core-5.10.x' of github.com:Silverpeas/Silverpeas-Core into core-5.10.x
on bug #3697, fixing conflict on jndi.properties