When somebody unintentionally adds the icefaces-ahs.jar to a web application archive. It throws a bunch of exceptions when it is deployed and accessed. Exceptions like icefaces.responseTopic not bound and such (because JMS was not configured on the target application server). We should improve this exception report explaining that the icefaces-ahs.jar is included in the archive and that the JMS is not configured correctly. Suggesting that if it was intentionally included the user should refer to the ICEfaces Developer's Guide on how to configure JMS, and that if it was unintentionally included the user should remove it from the archive.
Improvement
Major