[jira] [Comment Edited] (TOMEE-4049) Cannot Upgrade BouncyCastle libs due to incompatibility with Geronimo javamail

["Richard Zowalla (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TOMEE-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611017#comment-17611017 ] 

Richard Zowalla edited comment on TOMEE-4049 at 9/29/22 12:49 PM:
------------------------------------------------------------------

Sounds more like a Geronimo Mail problem than a problem related to TomEE. Does it work, if you exchange the javamail library used?


was (Author: rzo1):
Sounds more like a Geronimo Mail problem as a problem related to TomEE. Does it work, if you exchange the javamail library used?

> Cannot Upgrade BouncyCastle libs due to incompatibility with Geronimo javamail
> ------------------------------------------------------------------------------
>
>                 Key: TOMEE-4049
>                 URL: https://issues.apache.org/jira/browse/TOMEE-4049
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>            Reporter: Tim Clapp
>            Priority: Major
>         Attachments: Signature.java, pom.xml
>
>
> I'm using BouncyCastle + JavaMail to implement AS2 services.
>  
> I tried to upgrade the BouncyCastle libs to 1.6.* and 1.7.* and in both cases when I create a multi-part body, the signing of the message fails to return a digest.
>  
> I tracked down the problem to the geronimo lib which includes java.mail:
> geronimo-javamail_1.4_mail-1.9.0-alpha-2.jar (used in TomEE 7.1)
> geronimo-javamail_1.6_mail-1.0.1.jar (used in TomEE8)
>  
> If I remove the geronimo library, signing works as expected, but I cannot remove geronimo from TomEE as it will fail to start, so I'm in a bit of a pickle.
>  
> I'm currently running:
>  * TomEE 7.1 
>  * BC 1.54
>  * geronimo-javamail_1.4_mail-1.9.0-alpha-2.jar
>  
> I'm not sure how to get around this  incompatibility and looking for some help.
>  
> I've attached a pom+driver to demonstrate the issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)