Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Bug in jetty 9.x

There's nothing magic about lib/ext that makes those jars available to a webapp's classloader.
In Jetty 7, Jetty 8, and Jetty 9 the webapp classloader would isolate those lib/ext jars from that webapp.

Now, having said that, lib/ext is a popular and misused place to shove server side jars for things like JNDI resources (such as those needed to setup DataSource specific JNDI resources).

If that's what you want, then add this line to your `${jetty.base}/start.ini` (NOT your `${jetty.home}/stat.ini`)

--module=ext



--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Wed, Jan 28, 2015 at 11:15 PM, Mohan Ramu <rmdmohan27@xxxxxxxxx> wrote:
Hi ,

We have requirement for separating war with out dependency and jars in lib folder or jar of jars. When i try to deploy all the jar of jars or lib folder in ext that is throwing class not found exception. But the same thing is working when i use jetty 8.x. 
Jett 9.x is not supporting for deployment of dependency jars in lib/ext.

 
Thanks & Regards,
 
Mohan.R
Mob:9538977984
 
 

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top