I may have figured out what was causing the problem. I have a custom Servlet filter on my existing
webapp that does what amounts to URL rewriting on the HttpServletRequest object by moving
portions of the URL path to the query string as parameters. I commented out the filter and everything
started to work OK. Now this is a little strange because I only wrap the request and do not touch
the response in my filter. And it seems it was the response that was causing the problem, right?
With Maverick producing PDFs for me I can actually do away with this filter. The reason for having
it in the first place is to help a web spider archive portions of the site and hence the need to mess
around with this URL rewriting business. So, I think I may be in the clear but I'm still curious why
it was causing a problem in the first place.
Tim
Subject: RE: [Mav-user] Strange NullPointerException
Date: Wed, 19 Feb 2003 14:44:11 -0800
From: "Schnitzer, Jeff" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
This happens when the previous step (or view) never called
HttpServletResponse.getOutputStream() or getWriter(). I believe I
recently checked in a patch that prints a better error message in this
case.
Maybe the jsp page is misnamed? I would normally expect that to cause
getRequestDispatcher() to return null, but it would explain the problem.
What container/version are you using?
Jeff Schnitzer
[EMAIL PROTECTED]
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge [INVALID FOOTER]
