Jetty 7 but probably applies everywhere:

I have a continuation callback that sometimes generates an expected 
org.eclipse.jetty.io.EofException and I'm trying to figure out how I should be 
catching that.

The classes jetty has loaded aren't seen by the app's class loader, because 
they're in (I presume) ServerClasss. I can include the io jar in my webapp but 
that doesn't really help: the exceptions thrown by jetty aren't from the class 
my app sees since they're from jetty's class loader.

Should I be replacing ServerClasses and including the jetty classes/packages 
except io?

Or am I taking the wrong approach?
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to