Changed Fix Version(s) to 1.7.2

Changed Assignee Priority to P1

After the introduction of the handshake mechanism we should be able to reduce the amount of messages/exceptions more easily.

Following exception is seen when icefaces-ahs.jar is included in component-showcase:

ERROR - Exception sending context initialized event to listener instance of class com.icesoft.faces.util.event.servlet.ContextEventRepeater - org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/component-showcase]
java.lang.NoClassDefFoundError: javax/jms/JMSException
at com.icesoft.faces.util.event.servlet.MessagingContextEventPublisher.setUpMessageServiceClient(MessagingContextEventPublisher.java:139)
at com.icesoft.faces.util.event.servlet.MessagingContextEventPublisher.publish(MessagingContextEventPublisher.java:88)
at com.icesoft.faces.util.event.servlet.ContextEventRepeater.contextInitialized(ContextEventRepeater.java:203)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)

The last mentioned exception doesn't seem to be there anymore... (The exception was spotted using Tomcat by the way.)

Changed Fix Version(s) back to 1.7.2. We should really look into the handshake mechanism before pursuing this one.

Lowered Assignee Priority to P2 as it is dependent on the mentioned handshake mechanism.

A follow-up JIRA has been created to further address this issue (ICE-3522). Marking this one as FIXED.

When trying to adapt to AHS on Tomcat, an exception is thrown as the JMS API is not present on a default Tomcat install. I added a check to see if the JMS API is present before using the JMS API itself to try and adapt to the AHS environment.