Hi Steve,
Happy Holidays to you too.
jetty-7.0.2 is pretty old. Looking at the code for the
MultiPartFilter, it seems that perhaps the temp dir for the context
has not been set as a context attribute. That should be done by the
WebInfConfiguration class that is applied during deployment of the
Hi,
I maybe said that everything was fine a bit fast...
When I run the assembled war by maven (if it's from inside eclipse its ok)
I've got this exception when I try to display a jsp with jstl inside
The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved
in either web.xml or the
It appears to be this line:
MultipartConfigElement config = new
MultipartConfigElement(tempdir.getCanonicalPath(), _maxFileSize,
_maxRequestSize, _fileOutputBuffer);
Which means that tempdir is probably null for some reason. The line
appears in the jetty-8 branch; it was merged in from
some more traces (normally after ~ 800KB of data transfered)
org.eclipse.jetty.io.EofException
at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:954)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:274)
at
