Summary

Error Messages

 <pxErrorMessage>loader constraint violation: when resolving interface method "javax.mail.Part.setDataHandler(Ljavax/activation/DataHandler;)V" the class loader (instance of com/pega/pegarules/bootstrap/loader/PRAppLoader) of the current class, com/pega/platform/integrationcore/client/email/internal/javamail/JavaMailPart, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for the method's defining class, javax/mail/Part, have different Class objects for the type javax/activation/DataHandler used in the signature</pxErrorMessage>

Steps to Reproduce

1. Execute any functonal or  business scenario such that emails are sent to the recipients (users)
2. Generate the Correspondence and link to the work object. User does not receive emails
3. Open the correspondence generated for the work object. The status is 'Not Yet Sent'

Root Cause

The class loading strategy of Pega and of that of JBoss collide for the javax.activation classes that are provided both as an external library, coming from JBoss, and as part of the Java Runtime Library.

Resolution

<module xmlns="urn:jboss:module:1.3" name="javax.activation.api">

    <dependencies>

        <module name="javax.api" />

        <module name="javax.mail.api" optional="true">

            <imports><include path="META-INF"/></imports>

        </module>

        <module name="com.sun.xml.messaging.saaj" optional="true"/>

        <module name="org.jboss.ws.native.jbossws-native-core" optional="true"/>

        <module name="org.apache.cxf" optional="true"/>

<system export="true"><paths> <path name="javax/activation"/></paths></system>

    </dependencies>

<!--    <resources>

        <resource-root path="activation-1.1.1.redhat-5.jar"/>

    </resources>-->

</module>