Assuming you are using jetty via the distribution, the better thing to do is to make your own module that uses the javax.mail of your choice. Take a look at this issue: https://github.com/eclipse/jetty.project/issues/2960, particularly links to other issues where I describe how to make and use your own module.
You are correct that the change you have made, as it was in the webapps context xml file will not affect other applications. Jan On Mon, 29 Jul 2019 at 14:20, kapil gupta <[email protected]> wrote: > Hi, > > We are using jetty-9.4.14 which internally > use javax.mail.glassfish-1.4.1.v201005082020. Now we are using updated > version of javax.mail in our application and which was not being picked up. > So we made changes in application's context.xml as below: > > <Call name="prependSystemClass"> > <Arg>-javax.mail.</Arg> > </Call> > <Call name="prependServerClass"> > <Arg>javax.mail.</Arg> > </Call> > > This works fine, but I have one question. We have around 10 applications > and made this change only for one application, so this should not have an > impact on other applications? Is this the correct approach to the problem? > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users -- Jan Bartel <[email protected]> www.webtide.com *Expert assistance from the creators of Jetty and CometD*
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
