Resolve "ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-0.0.0.0-8080-3) SOAP request exception" in EngageOne and EngageOne Vault

Vault: 7.0M1p0002
EngageOne: GA-3.1.0.22998.34

Product Feature: General
Operating System: Windows 2008
Configuration: JBoss: jboss-5.1.0.GA-jdk6

Java: 1.6.0_45

Issue

EngageOne Correspondent fails to work in JBoss 5.1 if the "endorsed" folder required by E2VaultWS.war (from 7.0M1p0002) is copied into the "<JBOSS_Home>/lib/".

Admin appears to work normally, but when attempting to login to EO Correspondent there is no 'domain' dropdown and the server log for JBoss might contain errors like this:
--------------------------------------------------
2014-04-22 02:30:19,216 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-0.0.0.0-8080-3) SOAP request exception
java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl
--------------------------------------------------

Cause

EngageOne uses the default libs from JBoss 5.1 (jax-ws-2.2, servlet 2.5).

E2VaultWS uses jax-ws version 2.2.1.
 
When deploying together, they are conflict.

Resolution

UPDATED: November 13, 2017
The new version of 7.0M1p0003 (and later versions) includes the separate war files for different libs inside the package of E2VaultWS in different packages:
\war-full\E2VaultWS.war ==> including everything;
\war-jaxws\E2VaultWS.war ==> including only jax-ws-2.2.1 libs + e2vault.jar + log4j
\war\E2VaultWS.war ==> including e2vault.jar + log4j

For deployment on JBOSS 5.1, you should use \war-jaxws\E2VaultWS.war.

Update to version 7.0M1p0003 or later versions.