Many third party applications package api jars such as xml-apis jaxb-api, etc... These classes should be ignored as they will not work because some of the classes are contained in the JDK and some are part of the J2EE spec. Removing the jars will fix the issue, however that some times breaks the support of the application. Also the Spec says the app server shouldn't allow them to use JDK / J2EE api classes in their deployment.

We need the filteredPackage mechanism exposed for the EAR and EJB deployers as the WAR deployer has below. This will allow customers to deploy any standard J2EE application that contains these api classes if they add a filteredPackages in the deployers.

$JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml

<bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer">
<property name="relativeOrder">-1</property>
<property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
</bean>
...
<bean name="WarDeployer" class="org.jboss.web.tomcat.service.deployers.TomcatDeployer">
...
<property name="filteredPackages">javax.servlet,org.apache.commons.logging</property>
....
</bean>