<div dir="ltr"><div>At a guess I would say it is because modules import the META-INF directory by default, while when using jboss-deployment-structure.xml you need to explicitly add meta-inf="true".<br><br></div>Stuart<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 21, 2016 at 11:47 PM, Carl Harris <span dir="ltr"><<a href="mailto:ceharris414@me.com" target="_blank">ceharris414@me.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have a custom JavaMail provider installed as a module in Wildfly 10.<br>
<br>
In the configuration, I specify a mail session using the custom provider like this:<br>
<br>
<mail-session name="rcpt" jndi-name="FixedRecipient"><br>
<custom-server name="FixedRecipient"><br>
<!-- configuration properties hee --><br>
</custom-server><br>
</mail-session><br>
<br>
<br>
If I make the provider a global module in the configuration, a deployment can successfully use the provider.<br>
<br>
However, if I specify the provider as module dependency in jboss-deployment-structure.xml, when trying to create a javax.mail.Session using the provider, a NoSuchProviderException is thrown (as though the base Session implementation cannot find a META-INF/javamail.providers mapping that identifies the custom provider).<br>
<br>
I don't know whether specifying the provider as a deployment structure dependency should work or not, but it seems like it should.<br>
<br>
Can someone please explain?<br>
<br>
carl<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>