• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Multipart request with HttpServletResponseWrapper (java.lang.NullPointerException)

 
Csaba Palhidy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hy All,

Sorry, I don't speak very good English.
My problem:
-I do in Filter:

If the request type is multipart then I get an error message:

Only multipart request throw exception and if i skip the wrapper is good too.
Action is executed, get and set method is executed. Jsp creating throw the exception. (Struts 2)

Any idea?

Thanks,
Palidy
 
Joe Ess
Bartender
Posts: 9312
10
Linux Mac OS X Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch.

These lines in your error:

have me thinking this is a text resource problem. The File Upload Interceptor uses several text properties to display errors. Do you have those properties declared? (if that is the problem I would be surprised that it does not fail more gracefully).

 
Csaba Palhidy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hy hy!

Thanks
Joe Ess wrote:have me thinking this is a text resource problem. The File Upload Interceptor uses several text properties to display errors. Do you have those properties declared? (if that is the problem I would be surprised that it does not fail more gracefully).

Unfortunately, It's not help. Problem remains the same.
Any other idea?

If this running in debug mode, this drop exception in console too:
This step is thrown: WebAppServletContext.execute(ServletRequestImpl, ServletResponseImpl) line: 2183
 
Joe Ess
Bartender
Posts: 9312
10
Linux Mac OS X Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Unfortunately, It's not help. Problem remains the same.


I don't think so. The previous error was:


This error is:


So you fixed the text resource problem.
You have two problems:
1. Your request is failing for some reason.
2. You cannot communicate this error, which causes other errors.
Perhaps catching the exception thrown in doFilter and checking that exception's cause (invoke getCause, print its stack trace, then call getCause on it because exceptions can be chained together) would shed some light on the issue. I'd like to see your filter source too.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic