<div dir="ltr">standalone/lib/ext is where extension jars are loaded from. <div><br></div><div>Basically if a deployment contains an Extension-List entry in MANIFEST.MF then this is one of the places that is searched (see org.jboss.as.server.moduleservice.ExtensionIndexService for details). </div>
<div><br></div><div>The whole extension-index thing is pretty yuck, and we would always recommend you use static modules instead, but this is a standard thing and we are required by the EE platform spec to support it.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 9, 2013 at 4:44 PM, Jaikiran Pai <span dir="ltr"><<a href="mailto:jpai@redhat.com" target="_blank">jpai@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't recollect how the standalone/lib and standalone/lib/ext folders<br>
were being used or if they were used at all. Are those folders still<br>
relevant or is it OK to remove them from the binary?<br>
<br>
-Jaikiran<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" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>